From: SourceForge.net <no...@so...> - 2006-11-21 10:38:31
|
Feature Requests item #1600296, was opened at 2006-11-21 11:38 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350599&aid=1600296&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: None Group: None Status: Open Priority: 5 Private: No Submitted By: Frieder Ferlemann (frief) Assigned to: Nobody/Anonymous (nobody) Summary: #pragma xdataseg <name>, #pragma (x|i|o|p|)dataseg <name> () Initial Comment: while it is possible to specify the name of code and const segments (#pragma constseg <name> and #pragma codeseg <name>) there is no way to set the segment names for xdata, data, idata, pdata, or the data overlay segment. This would allow to address at least three rationales: a) easy use of noncontiguous xdata memory (as found f.e. in some USB devices) b) allowing to overlay data/xdata memory 'by hand' (addressing SDCC's shortcomings in handling the sparse data memory) "#pragma dataseg MY_SEGMENT (OVR,DATA)" with the optional bracketed argument passed to the linker (or "#pragma dataseg OSEG" which would map the data segment to the segment OSEG) c) allowing for a low overhead solution for "How to point to end of used memory?" as proposed by Russ in: http://www.8052.com/forum/read.phtml?id=128332 Ideally these pragmas would be compatible with #pragma save and #pragma restore, so existing source files wouldn't have to be ripped apart to be able to overlay specific functions (or to have their xdata located at specific segments). Greetings, Frieder ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350599&aid=1600296&group_id=599 |