didier wrote:
> Reusing the space occupied by a global variable would be very
> bad indeed. Is it what is happening here?
yes. sorry i wasn't clear in my earliest mail.
it happens because of the way sdcc treats "char at 0xf000 foo;".
it apparently doesn't actually enter "foo" into the symbol
Reusing the space occupied by a global variable would be very bad indeed. Is it
what is happening here?
Didier
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Maarten Brock
Sent: Tuesday, August 19, 2008 3:09 AM
To: sdcc-user@lists.sourceforge.net
Subjec
Hello,
I intend to use bit addressable area of the iram for storing a set of flags
as byte size variables. Something like fitting 8 flags in one memory
location and have freedom to access the whole as a byte or individual bit.
I tried defining something like;
idata at 0x20 unsigned char pqrs;
sb
Didier,
In this regard the keyword static has the same effect as making the
variable global. I guess Paul already made his variables global.
Paul,
Is it ok to initialize those manually located variables? If so, add an
initializer and check if overlaps still happen. A while ago I added this
disti
