avr-gcc-list
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [avr-gcc-list] definition of memeory section


From: Ebert, Rolf
Subject: RE: [avr-gcc-list] definition of memeory section
Date: Fri, 13 Feb 2004 10:49:00 +0100

Jörg Wunsch schrieb:
> Wolfgang Gschwendtner <address@hidden> wrote:
> 
> > section     size      addr
> > .data          0   8388864
> > .text      16684         0
> > .bss        1098   8388864
> > .noinit        0   8389962
> > .eeprom        0   8454144
> > .stab      25488         0
> > .stabstr    6944         0
> 
> ..data is initialized data.  Consumes RAM and ROM (for the 
> initializers).
> ..text is the executable code, plus ROM constants.  Consumes ROM.
> ..bss  is uninitialized data.  Consumes RAM, will be cleared 
> to 0 by the
>       the startup code.
> ..noinit is unititialized data.  Consumes RAM, will not be touched by
>       the startup code (IOW: survives a reset).
> ..eeprom is initialized data.  Consumes EEPROM, you gotta transfer the
>       data to EEPROM yourself using the programmer.
> ..stab and .stabstr contain debugging information only.  Will not be
>       transfered to the device, only meaningful to debuggers.
> 
> So your ROM consumption is the sum of .text + .data.  Your RAM
> consumption is the sum of .data + .bss + .noinit, plus any dynamic
> memory you might use, plus the stack.

Most of that info I knew already or had heard of it before.  I was just
wondering if that is some kind of knowledge that "every real programmer"
just knows, or is that documented somewhere.

    Rolf


reply via email to

[Prev in Thread] Current Thread [Next in Thread]