Re: [avr-gcc-list] AVR-GCC question

[Joerg Wunsch]

"Daniel O'Connor" <address@hidden> wrote:

> I think the fundamental problem is that C wasn't designed for
> split architectures like the AVR so you are forced into using
> hacks to get it to work.

Exactly.  There's so far no standardized way to handle multiple memory
spaces, only a standard proposal.  Even there, the default memory
space must be compatible with the standard functions (like those from
string.h), so unless the default memory space uses something like a
`generic pointer' model (IOW, late binding where the actual physical
memory space is only decided about at run-time), it's still not
possible to default string literals to ROM.

> ie on say, a HC12, none of this is an issue because it behaves much
> more like a "normal" system.

Same for the TI MSP430 controller.

The C standard always (*) allowed it to have string literals in
read-only memory locations, but they need to be compatible with the
respective standard library functions, as well as with other string
objects in RAM.

-- 
cheers, J"org               .-.-.   --... ...--   -.. .  DL8DTL

http://www.sax.de/~joerg/                        NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)