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

[Paul Schlie]

Sorry, meant:

 Nor seem to be dependant on particular "GCC" versions, ...


> From: Paul Schlie <address@hidden>
> Date: Mon, 17 Jan 2005 18:20:00 -0500
> To: Joerg Wunsch <address@hidden>, <address@hidden>
> Subject: Re: [avr-libc-dev] [bugs #4101] setjmp/longjmp destroy changes in
> global registers
> 
>> From: Joerg Wunsch <address@hidden>
>> 
>> Anyway, as GCC 4.0 has not yet been released, we cannot release it in
>> a version of avr-libc before.  We could commit it to CVS already, but
>> then we'd have to require any CVS users to upgrade to pre-4.0
>> experimental versions of GCC, which I'd rather like to avoid.
>> 
>> I'll see to produce a pre-4 GCC version for my own tests though.
>> 
>> -- 
> 
> Understood, however inspecting other setjump.s implementations for
> other cpu's in newlib, I notice they also don't seem to save globals,
> Nor seem to be dependant on particular cpu versions, wonder if r3-r17
> should never have been saved by setjump?
> 
> (all seem most similar to the newly proposed patched setjump,
>  although recognize that there may be some functionality missing
>  in avr.h/c which correct behavior is dependant on, but it's not
>  clear that this is the case?)
> _______________________________________________
> AVR-libc-dev mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/avr-libc-dev