This is the mail archive of the
mailing list for the GCC project.
Re: avoid unnecessary register saves for setjmp
- From: Richard Earnshaw <rearnsha at arm dot com>
- To: "Zack Weinberg" <zack at codesourcery dot com>
- Cc: Andrew Pinski <pinskia at physics dot uc dot edu>, Jim Wilson <wilson at specifixinc dot com>, gcc-patches at gcc dot gnu dot org, Richard dot Earnshaw at arm dot com
- Date: Fri, 28 Nov 2003 09:11:10 +0000
- Subject: Re: avoid unnecessary register saves for setjmp
- Organization: ARM Ltd.
- Reply-to: Richard dot Earnshaw at arm dot com
> Andrew Pinski <firstname.lastname@example.org> writes:
> > On Nov 27, 2003, at 00:01, Zack Weinberg wrote:
> >> I'm going to take this opportunity to throw in a suggestion I've made
> >> before, which is that setjmp/longjmp should - always, not just when
> >> special variants are used - be converted by the front end into
> >> invocations of the exception-unwinding facility, which gives us tons
> >> more control. (Obviously this only works with DWARF2 exception
> >> handling.)
> > But what about backwards compatibility aka use of setjmp/longjmp
> > through libraries,
> This is a major stumbling block, yes.
Not to mention compatibility with objects built with other compilers.