From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7235 invoked by alias); 31 Mar 2004 02:03:26 -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 7043 invoked from network); 31 Mar 2004 02:03:24 -0000 Received: from unknown (HELO boden.synopsys.com) (198.182.44.79) by sources.redhat.com with SMTP; 31 Mar 2004 02:03:24 -0000 Received: from mother.synopsys.com (mother.synopsys.com [146.225.100.171]) by boden.synopsys.com (Postfix) with ESMTP id 0F10CDC6C; Tue, 30 Mar 2004 18:03:17 -0800 (PST) Received: from piper.synopsys.com (localhost [127.0.0.1]) by mother.synopsys.com (8.9.1/8.9.1) with ESMTP id SAA10107; Tue, 30 Mar 2004 18:03:23 -0800 (PST) Received: (from jbuck@localhost) by piper.synopsys.com (8.11.6/8.11.6) id i2V23Nv21687; Tue, 30 Mar 2004 18:03:23 -0800 X-Authentication-Warning: piper.synopsys.com: jbuck set sender to Joe.Buck@synopsys.com using -f Date: Wed, 31 Mar 2004 07:43:00 -0000 From: Joe Buck To: Jim Wilson Cc: jlkjr@bioleap.com, gcc@gcc.gnu.org Subject: Re: Floating Point Exception Handling Message-ID: <20040330180323.A21493@synopsys.com> References: <1080326140.6169.18.camel@BioLeapRD.gateway.2wire.net> <406A22B7.7030106@specifixinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <406A22B7.7030106@specifixinc.com>; from wilson@specifixinc.com on Tue, Mar 30, 2004 at 05:45:27PM -0800 X-SW-Source: 2004-03/txt/msg01738.txt.bz2 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++. On Tue, Mar 30, 2004 at 05:45:27PM -0800, Jim Wilson wrote: > 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. It would require rather deep surgery, I think, to make this work. G++ is not currently designed around the assumption that any floating point instruction might throw an exception, which is pretty much what you would need for such an idea to work. It's probably a better idea to use non-signaling Inf and NaN values, test for them at appropriate points and explicitly throw exceptions.