public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/33799] Return value's destructor not executed when a local variable's destructor throws Date: Thu, 02 Nov 2023 20:01:58 +0000 [thread overview] Message-ID: <bug-33799-4-ZufY2EjHAn@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-33799-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=33799 --- Comment #23 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The trunk branch has been updated by Jason Merrill <jason@gcc.gnu.org>: https://gcc.gnu.org/g:ae07265381d934ee97fb1ce8915731158c91babc commit r14-5086-gae07265381d934ee97fb1ce8915731158c91babc Author: Jason Merrill <jason@redhat.com> Date: Mon Oct 30 17:44:54 2023 -0400 c++: retval dtor on rethrow [PR112301] In r12-6333 for PR33799, I fixed the example in [except.ctor]/2. In that testcase, the exception is caught and the function returns again, successfully. In this testcase, however, the exception is rethrown, and hits two separate cleanups: one in the try block and the other in the function body. So we destroy twice an object that was only constructed once. Fortunately, the fix for the normal case is easy: we just need to clear the "return value constructed by return" flag when we do it the first time. This gets more complicated with the named return value optimization, since we don't want to destroy the return value while the NRV variable is still in scope. PR c++/112301 PR c++/102191 PR c++/33799 gcc/cp/ChangeLog: * except.cc (maybe_splice_retval_cleanup): Clear current_retval_sentinel when destroying retval. * semantics.cc (nrv_data): Add in_nrv_cleanup. (finalize_nrv): Set it. (finalize_nrv_r): Fix handling of throwing cleanups. gcc/testsuite/ChangeLog: * g++.dg/eh/return1.C: Add more cases.
next prev parent reply other threads:[~2023-11-02 20:02 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-33799-4@http.gcc.gnu.org/bugzilla/> 2013-11-28 11:18 ` redi at gcc dot gnu.org 2013-11-28 12:15 ` temporal at gmail dot com 2020-04-20 3:30 ` mm-nospam at outlook dot co.nz 2020-04-20 9:24 ` redi at gcc dot gnu.org 2020-05-07 11:56 ` jakub at gcc dot gnu.org 2020-07-23 6:52 ` rguenth at gcc dot gnu.org 2021-04-08 12:02 ` rguenth at gcc dot gnu.org 2022-01-06 14:31 ` jason at gcc dot gnu.org 2022-01-07 0:26 ` cvs-commit at gcc dot gnu.org 2022-02-01 22:51 ` jason at gcc dot gnu.org 2023-06-07 1:33 ` cvs-commit at gcc dot gnu.org 2023-11-02 20:01 ` cvs-commit at gcc dot gnu.org [this message] 2023-11-17 0:21 ` cvs-commit at gcc dot gnu.org 2023-11-17 0:21 ` cvs-commit at gcc dot gnu.org 2023-11-17 0:21 ` cvs-commit at gcc dot gnu.org 2023-11-17 0:21 ` cvs-commit at gcc dot gnu.org 2023-12-20 17:31 ` cvs-commit at gcc dot gnu.org 2024-01-24 19:39 ` cvs-commit at gcc dot gnu.org 2024-01-24 19:40 ` cvs-commit at gcc dot gnu.org 2007-10-17 11:31 [Bug c++/33799] New: " bitti at iki dot fi 2007-10-17 12:03 ` [Bug c++/33799] " rguenth at gcc dot gnu dot org 2007-10-17 12:21 ` bitti at iki dot fi 2007-10-17 17:07 ` jason at gcc dot gnu dot org 2008-09-19 12:14 ` bitti at iki dot fi
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-33799-4-ZufY2EjHAn@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: linkBe 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).