public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joerg.richter@pdv-fs.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/113767] New: Missing Destructor Call with goto and return value
Date: Mon, 05 Feb 2024 13:19:25 +0000	[thread overview]
Message-ID: <bug-113767-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 113767
           Summary: Missing Destructor Call with goto and return value
           Product: gcc
           Version: 13.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: joerg.richter@pdv-fs.de
  Target Milestone: ---

#include <cstdio>

struct S
{

    S()
    {
      printf( "Cons\n" );
    }

    ~S()
    {
      printf( "Dest\n" );
    }
};

S func()
{
  bool first = true;

restart:
  S ss;
  if( first )
  {
    first = false;
    goto restart;
  }
  return ss;
}

int main()
{
    func();
}

Output:
Cons
Cons
Dest

Expected Output:
Cons
Dest
Cons
Dest


https://godbolt.org/z/9n6nnv18P

Seems to be fixed in trunk but not on any released branch. Can the fix be
integrated to the released branches?

             reply	other threads:[~2024-02-05 13:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-05 13:19 joerg.richter@pdv-fs.de [this message]
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

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@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).