From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12841 invoked by alias); 31 Mar 2004 09:09:18 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 12828 invoked from network); 31 Mar 2004 09:09:17 -0000 Received: from unknown (HELO mta08-svc.ntlworld.com) (62.253.162.48) by sources.redhat.com with SMTP; 31 Mar 2004 09:09:17 -0000 Received: from cuddles.cambridge.redhat.com ([81.96.64.123]) by mta08-svc.ntlworld.com (InterMail vM.4.01.03.37 201-229-121-137-20020806) with ESMTP id <20040331090918.OYOU5004.mta08-svc.ntlworld.com@cuddles.cambridge.redhat.com> for ; Wed, 31 Mar 2004 10:09:18 +0100 Received: from redhat.com (localhost.localdomain [127.0.0.1]) by cuddles.cambridge.redhat.com (8.12.8/8.12.8) with ESMTP id i2V98ECL003992; Wed, 31 Mar 2004 10:08:24 +0100 Received: (from aph@localhost) by redhat.com (8.12.8/8.12.8/Submit) id i2V98D24003988; Wed, 31 Mar 2004 10:08:13 +0100 From: Andrew Haley MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16490.35452.355947.450755@cuddles.cambridge.redhat.com> Date: Wed, 31 Mar 2004 12:14:00 -0000 To: jlkjr@bioleap.com Cc: Jim Wilson , gcc@gcc.gnu.org Subject: Re: Floating Point Exception Handling In-Reply-To: <406A22B7.7030106@specifixinc.com> References: <1080326140.6169.18.camel@BioLeapRD.gateway.2wire.net> <406A22B7.7030106@specifixinc.com> X-SW-Source: 2004-03/txt/msg01755.txt.bz2 Jim Wilson writes: > John L. Kulp wrote: > > I'd like to get connected with whomever is working on topics like the > > interaction between SIGFPE handlers and try/catch stack unwinding in > > C++. I suppose the person with the most experience with unwinding and signal handlers would be me. > There are few people expert in this area, and they are all very busy > people. There may not be anyone who has time to help you. > > Unwinding from signal handlers should work fine for any IA-64 target. > For other targets, it is probably iffy. Our EH support was designed for > C++ which does not need this. It has been expanded to support Java > which does need this, but this requires special options > (-fnon-call-exceptions), and probably still needs more work to handle > all cases. I'm not aware of any current problems with unwinding from SIGFPE handlers. However, we don't actually do this on many gcj targets because we haven't made it a big priority. Andrew.