Re: [avr-gcc-list] avr-gcc internals and generation of object files

[Joerg Wunsch]

Torleif Sandnes <address@hidden> wrote:

> 1. How are the mapping to AVR specific segments performed in
> avr-gcc?  (flash, eeprom, sram..)

GCC isn't really prepared to handle Harvard architecture CPUs, it
basically can only handle a single address space.

AVR-GCC circumvents this problem by using offsets for the SRAM and
EEPROM locations (0x800000 and 0x810000 resp.).

> 2. Will avr-gcc always produce sections in an object file, or can
> this be avoided, just producing the program headers.

GCC will (IMHO) always produce sections, and people even tend to want
to create additional sections of their own (e. g. in order to combine
the bootloader and standard application code, or to create an
additional memory section for variables located in external RAM).

> 3. Will an avr-gcc outputting dwarf debug information behave any
> different in these contexts?

Probably not, except for the DWARF debugging info sections
(obviously).  The sections with memory contents (.text, .data, .bss,
plus user-defined sections) are pretty standard for C compilers from
an historical point of view.

-- 
J"org Wunsch                                           Unix support engineer
address@hidden        http://www.interface-systems.de/~j/