public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jim Wilson <wilson@specifixinc.com>
To: jlkjr@bioleap.com
Cc: gcc@gcc.gnu.org
Subject: Re: Floating Point Exception Handling
Date: Wed, 31 Mar 2004 07:27:00 -0000	[thread overview]
Message-ID: <406A22B7.7030106@specifixinc.com> (raw)
In-Reply-To: <1080326140.6169.18.camel@BioLeapRD.gateway.2wire.net>

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++.

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.

You might try looking at the optional libunwind package.  This was 
primarily written to support IA-64 target, but it also has some support 
for gcc's DWARF2 CFI based unwinders.  Also, you might find other people 
interested in the same topic on the libunwind mailing list.  See
	http://www.hpl.hp.com/research/linux/libunwind/
-- 
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com

  reply	other threads:[~2004-03-31  1:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-26 21:03 John L. Kulp
2004-03-31  7:27 ` Jim Wilson [this message]
2004-03-31  7:43   ` Joe Buck
2004-03-31 12:14   ` Andrew Haley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=406A22B7.7030106@specifixinc.com \
    --to=wilson@specifixinc.com \
    --cc=gcc@gcc.gnu.org \
    --cc=jlkjr@bioleap.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).