From: Eric Botcazou <botcazou@adacore.com>
To: Ian Lance Taylor <iant@google.com>
Cc: Helmut Zeisel <HZ2012@gmx.at>, gcc@gcc.gnu.org, gcc@gcc.gnu.org
Subject: Re: When do I need -fnon-call-exceptions?
Date: Wed, 07 Jun 2023 21:35:20 +0200 [thread overview]
Message-ID: <1899746.taCxCBeP46@fomalhaut> (raw)
In-Reply-To: <CAKOQZ8zSCuiqarM69J+60171X6s5thK+ycoHX54ym9bCUtaWdA@mail.gmail.com>
> On x864 Linux -fasynchronous-unwind-tables is the default. That is
> probably sufficient to make your test case work.
The testcase g++.dg/torture/except-1.C you recently added to the testsuite
does not pass at all if -fnon-call-exceptions is not specified (and does not
pass with optimization if -fno-delete-dead-exceptions is not specified).
--
Eric Botcazou
prev parent reply other threads:[~2023-06-07 19:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 17:08 Helmut Zeisel
2023-06-07 19:04 ` Ian Lance Taylor
2023-06-07 19:35 ` Eric Botcazou [this message]
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=1899746.taCxCBeP46@fomalhaut \
--to=botcazou@adacore.com \
--cc=HZ2012@gmx.at \
--cc=gcc@gcc.gnu.org \
--cc=iant@google.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).