From: SourceForge.net <no...@so...> - 2007-02-01 17:02:14
|
Bugs item #1649973, was opened at 2007-02-01 17:36 Message generated for change (Comment added) made by maartenbrock You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100599&aid=1649973&group_id=599 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: linker >Group: known bugs >Status: Closed >Resolution: Out of Date Priority: 5 Private: No Submitted By: nitrix06 (nitrix06) >Assigned to: Maarten Brock (maartenbrock) Summary: code overlap no error in linker Initial Comment: Hi, In the attached examples files i have a section for USB descriptors: usb_descr_area which i map to 0x200 (see dscr.a51) I also tell the linker i want my code to start at 0x200... Even though this is stupid the linker does not generate an error and report in the map file the usb_descr_area being at 0x200 as well as the HOME area.... Actually the usb_descr_area is not shown as starting at 0x200 but the labels inside this file like _DeviceDescr are... Regards, Nicolas. ---------------------------------------------------------------------- >Comment By: Maarten Brock (maartenbrock) Date: 2007-02-01 18:02 Message: Logged In: YES user_id=888171 Originator: NO This behaviour is documented in the manual for SDCC 2.6.0. The latest snapshot of SDCC 2.6.4 however does allocate for absolutely placed variables in code space. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100599&aid=1649973&group_id=599 |