Thank you; I had not noticed .noinit specifically before, and misinterpreted
a too-rapid scan of the source. Data marked in "noinit" does indeed appear
in RAM, following the unqualified data which goes in the .bss section and is
initialized. Delete that first sentence and I think the rest of what I
wrote is correct (if not necessarily relevant).
I suspect assigning a specific address using asm, though, overrides this and
makes the section irrelevant. In any case, I believe there may need to be a
different linker script used for these devices when the USB is to be
enabled, to ensure program variables don't end up creeping in the area
reserved for USB. Yet another variation point....
Peter
On Sat, Nov 20, 2010 at 2:46 PM, Chris Liechti <cliec...@gmx.net> wrote:
> Am 20.11.2010 20:38, schrieb Peter Bigot:
> > To expand on what Chris said:
> >
> > The .noinit section is an alias for the .infomemnobits section.
>
> i do not think so.
>
> .noinit is the name of a section in RAM. it is specified in the linker
> scripts.
>
> at least, that was the case for mspgcc (3) and if the behavior was
> different, a number of programs of mine would no longer work ;-)
>
> chris
>
------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3.
Spend less time writing and rewriting code and more time creating great
experiences on the web. Be a part of the beta today
http://p.sf.net/sfu/msIE9-sfdev2dev
_______________________________________________
Mspgcc-users mailing list
Mspgcc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mspgcc-users
