[sdcc-devel] [ sdcc-Bugs-954959 ] Bad xdata init

[SourceForge.net <no...@so...>]

Bugs item #954959, was opened at 2004-05-16 13:31
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100599&aid=954959&group_id=599

Category: msc51(8051) target
Group: fixed
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: Bad xdata init

Initial Comment:
I've run into what I believe is a bug. Maybe there is 
something I just overlooked.

I'm using a system on which code is in "external 
memory", thus code and external RAM are sharing a 
common space.

I've used the right options to select the code start and 
xram start (and size):

--iram-size 256 --xram-loc 0x1740 --xram-size 1024 --code-loc 0x0000 --code-size 5952

The linker puts everything in the right place, but there is 
a problem with the run-time library: during initialization 
of the external RAM, the variables that are in XRAM are 
initialized with zeros (which is OK), but instead of 
starting at the address mentioned in --xram-loc, it 
seems to start at 0x0000, which then overwrites some 
of the code on my system. I think this shouldn't be 
happening. Or should we re-compile the run-time library 
in a case like this? If so, how? I think this is not at all 
clearly stated in the docs (as far as I've read).

For the time being, I use the option --no-xinit-opt and 
handle things myself, but I think there is something 
wrong.

Thanks for considering this "bug" report.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100599&aid=954959&group_id=599