public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/97720] throw in try in noexcept fn calls terminate without handling the exception
Date: Sun, 04 Jun 2023 02:11:18 +0000 [thread overview]
Message-ID: <bug-97720-4-N5kfE2fKJ5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97720-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97720
Jason Merrill <jason at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Depends on|95741 |
Status|NEW |ASSIGNED
Target Milestone|--- |14.0
Assignee|unassigned at gcc dot gnu.org |jason at gcc dot gnu.org
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=95741
--- Comment #9 from Jason Merrill <jason at gcc dot gnu.org> ---
(In reply to m101010a from comment #6)
> I don't believe there's a way to solve PR55918 without modifying the
> personality function in some way
I agree; for C++17 (when dynamic exception specifications were removed) and
later we could use an alternate personality function that knows that an
exception-specification is noexcept, so we can just call terminate.
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95741
[Bug 95741] Optimization skips destructor and calls terminate directly
next prev parent reply other threads:[~2023-06-04 2:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 20:54 [Bug c++/97720] New: Sometimes std::current_exception does not work properly in the terminate handler m101010a at gmail dot com
2020-11-04 21:20 ` [Bug c++/97720] " redi at gcc dot gnu.org
2020-11-05 2:02 ` m101010a at gmail dot com
2022-12-16 16:52 ` m101010a at gmail dot com
2023-05-22 21:34 ` [Bug c++/97720] throw in try in noexcept fn calls terminate without handling the exception jason at gcc dot gnu.org
2023-05-23 3:52 ` jason at gcc dot gnu.org
2023-05-23 17:20 ` m101010a at gmail dot com
2023-06-04 1:49 ` cvs-commit at gcc dot gnu.org
2023-06-04 2:08 ` jason at gcc dot gnu.org
2023-06-04 2:11 ` jason at gcc dot gnu.org [this message]
2024-05-07 7:39 ` rguenth at gcc dot gnu.org
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=bug-97720-4-N5kfE2fKJ5@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).