[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [avr-gcc-list] ATmega256x trampolines? (Was: Why is there 1200 bytes
From: |
Erik Christiansen |
Subject: |
Re: [avr-gcc-list] ATmega256x trampolines? (Was: Why is there 1200 bytes of zeroes in my code?) |
Date: |
Wed, 21 Mar 2007 19:42:06 +1100 |
User-agent: |
Mutt/1.5.9i |
On Wed, Mar 21, 2007 at 07:07:24AM +0100, Joerg Wunsch wrote:
>
> > *fill* 0x000020f3 0x1 00=20
> > 0x000020f4 __trampolines_start =3D .=20
> > *(.trampolines)=20
> > .trampolines 0x000020f4 0x0 linker stubs=20
> > *(.trampolines*)=20
> > 0x000020f4 __trampolines_end =3D .=20
> > *(.jumptables)=20
> > *(.jumptables*)=20
>
> Obviously, this is somehow related to the linker stubs, but the
> question is how the space allocation is calculated.
Is it possible to invoke avr-gcc with "-Wl,-verbose" in the winavr
environment, so the we can see the linker script being used? (It would
be enlightening to see what it directs for these sections.)
Erik