From: Helmut Zeisel <HZ2012@gmx.at>
To: gcc@gcc.gnu.org
Subject: When do I need -fnon-call-exceptions?
Date: Wed, 7 Jun 2023 19:08:01 +0200 [thread overview]
Message-ID: <trinity-c6ee9039-f130-4c39-9346-892ab24ab654-1686157681645@3c-app-gmx-bap67> (raw)
I wrote some simple program that set a signal handler for SIGFPE, throws a C++ exception in the signal handler
and catches the exception.
I compiled with and without -fnon-call-exceptions (on x64 Linux).
In both cases, the result was the same: the exception was caught and the destructors were called as expected.
I also tried "-fno-non-call-exceptions -fexceptions" and got the same result.
My question: when do I really need -fnon-call-exceptions?
Is there some simple program where I can see the difference whether it is on or off??
Helmut
next reply other threads:[~2023-06-07 17:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 17:08 Helmut Zeisel [this message]
2023-06-07 19:04 ` Ian Lance Taylor
2023-06-07 19:35 ` Eric Botcazou
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=trinity-c6ee9039-f130-4c39-9346-892ab24ab654-1686157681645@3c-app-gmx-bap67 \
--to=hz2012@gmx.at \
--cc=gcc@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).