Re: [avr-libc-dev] [bugs #4101] setjmp/longjmp destroy changes in global registers

[Joerg Wunsch]

As Paul Schlie wrote:

> Upon thinking about things a little further, it appears that the
> true conflict between the use of set/longjump and the declaration of
> compile time reserved global registers, isn't with the definition of
> set/longjump itself, but with the definition of a C function library
> in which the functions implemented in assembly code presume a fixed
> call ABI, which precludes the otherwise safe exclusion of
> caller-saved registers being declared/reserved as being global
> registers, as would automatically be excluded from allocation during
> the compilation of C based implementations.

You're 100 % off here.

-- 
cheers, J"org               .-.-.   --... ...--   -.. .  DL8DTL

http://www.sax.de/~joerg/                        NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)