This is the mail archive of the
mailing list for the binutils project.
Re: [avr-gcc-list] [Patch, avr] Shrink interrupt vector table down to last used entry
- From: Oleksandr Redchuk <real at real dot kiev dot ua>
- To: "Weddington, Eric" <Eric dot Weddington at atmel dot com>
- Cc: "Selvaraj, Senthil_Kumar" <Senthil_Kumar dot Selvaraj at atmel dot com>, "binutils at sourceware dot org" <binutils at sourceware dot org>, "avr-gcc-list at nongnu dot org" <avr-gcc-list at nongnu dot org>, "Wunsch, Joerg" <Joerg dot Wunsch at atmel dot com>
- Date: Thu, 14 Feb 2013 18:43:39 +0200
- Subject: Re: [avr-gcc-list] [Patch, avr] Shrink interrupt vector table down to last used entry
- References: <20130214104803.GA904@atmel.com> <F4ADC872C7AFBE49A9CEDE5C75191C274059CF68@dvrmbx01>
2013/2/14 Weddington, Eric <Eric.Weddington@atmel.com>:
> If this "optimization" were put in place, then there is the potential
> that these wrongly-enable interrupts could vector off to some part of the application code,
> start executing it, without ever having a return from interrupt (RETI), and could wreak havoc
> with the rest of the system, and also making debugging such a system that much harder.
> I would have to see evidence that these devices, especially the XMEGAs, which typically
> have more code space, are so constrained that such an optimization is warranted over
> the safety of the overall system.
How about "no-any-interrupt" (and no sei() in code) programs for small
micro like tiny13 or tiny261 ?
Anyway, one must explicitly enable this feature by --shrink-ivt swicth
for shut in foot.
For existing projects will not be any safety problems.