[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [avr-gcc-list] Overlong interrupt vector table
From: |
Weddington, Eric |
Subject: |
RE: [avr-gcc-list] Overlong interrupt vector table |
Date: |
Tue, 3 Feb 2009 15:23:11 -0700 |
> -----Original Message-----
> From:
> address@hidden
> [mailto:address@hidden
> org] On Behalf Of Richard F
> Sent: Tuesday, February 03, 2009 2:58 PM
> To: address@hidden
> Subject: Re: [avr-gcc-list] Overlong interrupt vector table
>
> Now I understand the reason for the "extra" table entries, I was
> thinking that the jump table solution would be the smallest,
> so I didn't
> think there was any likely code size improvement. But using
> -fno-jump-tables option does make the code very slightly
> smaller in my
> case (just 4 bytes).
>
> I think it would be helpful in future versions if the compiler could
> output a separate table and name it, like it does for PROGMEM tables.
> Then it's clear what's in each table. Is that possible?
>
What does your map file show?