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++/113767] [11/12/13 Regression] Missing Destructor Call with goto and return value
Date: Mon, 05 Feb 2024 18:20:10 +0000	[thread overview]
Message-ID: <bug-113767-4-JCkOvfr251@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113767-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113767

Jason Merrill <jason at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |DUPLICATE
             Status|ASSIGNED                    |RESOLVED

--- Comment #2 from Jason Merrill <jason at gcc dot gnu.org> ---
The fix on the branches is just to disable NRV in the presence of backward
goto, as the fix on the trunk was too involved to backport.

So this testcase no longer puts ss in the return slot in 11/12/13, but instead
returns a copy; the extra destructor call is for the copy.  It looks mismatched
because there's no user-defined copy constructor to add another "Cons" line;
adding that makes it look better.

*** This bug has been marked as a duplicate of bug 92407 ***

      parent reply	other threads:[~2024-02-05 18:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-05 13:19 [Bug c++/113767] New: " joerg.richter@pdv-fs.de
2024-02-05 15:46 ` [Bug c++/113767] [11/12/13 Regression] " ppalka at gcc dot gnu.org
2024-02-05 16:37 ` jason at gcc dot gnu.org
2024-02-05 16:38 ` jason at gcc dot gnu.org
2024-02-05 18:20 ` jason at gcc dot gnu.org [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=bug-113767-4-JCkOvfr251@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).