22 Jul
2016
22 Jul
'16
7:25 a.m.
Dear Simon
In message CAPnjgZ3w6xn7omKK0V077iGWNVr8L71ZE26rnY_6A5C0pZ1w7A@mail.gmail.com you wrote:
I'm really not sure about this. The large binary suggests that you have code/data at 0 and at 0xfe000000, which seems wrong. So the image is trying to bridge the gap and ends up being huge.
Probaly the code / data overflows at 0xFFFFFFFF and wraps arount to continue at 0x0 which cuses the huge image size. We have seen this before with somme tool chain versions and some (usually sub-optimal) optimizer settings.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Wenn das dann in die Hose geht, nehme ich es auf meine Kappe.
-- Rudi Völler, 15. Nov 2003