public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: rodrigc@gcc.gnu.org
To: Hugo.Mildenberger@topmail.de, gcc-bugs@gcc.gnu.org,
	gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, rodrigc@gcc.gnu.org
Subject: Re: c++/661: -fsjlj-exceptions breaks programs using exception specifications
Date: Fri, 28 Sep 2001 17:03:00 -0000	[thread overview]
Message-ID: <20010929000307.7589.qmail@sourceware.cygnus.com> (raw)

Synopsis: -fsjlj-exceptions breaks programs using exception specifications

State-Changed-From-To: open->closed
State-Changed-By: rodrigc
State-Changed-When: Fri Sep 28 17:03:07 2001
State-Changed-Why:
    In gcc 3.0 and above, you now need configure gcc to use
    sjlj exceptions when you build it.  It is no longer
    a run-time option.
    
    This will compile libgcc with sjlj exceptions enabled.
    
    In addition, the -fasynchronous-exceptions flag
    has been renamed to -fnon-call-exceptions.
    Refer to the gcc 3.0 documentation.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=661&database=gcc


                 reply	other threads:[~2001-09-28 17:03 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20010929000307.7589.qmail@sourceware.cygnus.com \
    --to=rodrigc@gcc.gnu.org \
    --cc=Hugo.Mildenberger@topmail.de \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    /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).