This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: avoid unnecessary register saves for setjmp
- From: Gabriel Dos Reis <gdr at integrable-solutions dot net>
- To: Chris Lattner <sabre at nondot dot org>
- Cc: Zack Weinberg <zack at codesourcery dot com>, Andrew Haley <aph at redhat dot com>, <Richard dot Earnshaw at arm dot com>, Jim Wilson <wilson at specifixinc dot com>, <gcc-patches at gcc dot gnu dot org>
- Date: 27 Nov 2003 21:26:01 +0100
- Subject: Re: avoid unnecessary register saves for setjmp
- Organization: Integrable Solutions
- References: <Pine.LNX.4.44.0311271354320.4388-100000@nondot.org>
Chris Lattner <sabre@nondot.org> writes:
| LIFO order. I guess that people are used to not having longjmp work
| "correctly"? :)
Yup. In effect, the C++ standard says nothing about mixing
setjmp/longjmp with notions like construction and destruction --
meaning it is undefined. C++ tries to provide those non local gotos
in structrured manner through exception handling -- which gives better
guarantees.
-- Gaby