[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
AW: [avr-gcc-list] Bootloader interrupt callbacks
From: |
Sven Schlender |
Subject: |
AW: [avr-gcc-list] Bootloader interrupt callbacks |
Date: |
Mon, 18 May 2009 12:06:53 +0200 |
Hi Eric,
thanks for quick reply.
> Do you really have problems or where you only preoccupied about
> this case ?
No really problems yet, only thinking about this.
> In fact, you are wondering how the compiler should threat function calls
> from an ISR.
> I do not see any difference between callback or direct call.
> Every procedure should preserve/restore any register, except r18-r31 and
> take care of r1, r0.
Yes: Pushing and popping all the registers would solve the problem. But: We
have some quick ISRs, which are written in assembler. Pushing and popping
all registers would be true overkill if you only need a few. Thats why I
thought about a way, where callback functions store and resolve the used
registers by its own.
Regards,
Sven
- Re: [avr-gcc-list] mcall-prologues completely broken for >128k, (continued)
- Message not available
- Re: [avr-gcc-list] mcall-prologues completely broken for >128k, Dmitry K., 2009/05/13
- Re: [avr-gcc-list] mcall-prologues completely broken for >128k, Dmitry K., 2009/05/14
- Re: [avr-gcc-list] mcall-prologues completely broken for >128k, Sean D'Epagnier, 2009/05/14
- Re: [avr-gcc-list] mcall-prologues completely broken for >128k, Dmitry K., 2009/05/16
- Re: [avr-gcc-list] mcall-prologues completely broken for >128k, Sean D'Epagnier, 2009/05/16
- [avr-gcc-list] Bootloader interrupt callbacks, Sven Schlender, 2009/05/18
- Re: [avr-gcc-list] Bootloader interrupt callbacks, Eric Pasquier, 2009/05/18
- AW: [avr-gcc-list] Bootloader interrupt callbacks,
Sven Schlender <=
- [avr-gcc-list] ATmega128RFA1, Sven Schlender, 2009/05/19
- RE: [avr-gcc-list] ATmega128RFA1, Weddington, Eric, 2009/05/25