public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ppalka 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 15:46:09 +0000 [thread overview] Message-ID: <bug-113767-4-fLC4Khlm1v@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 Patrick Palka <ppalka at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords|needs-bisection | Target Milestone|--- |13.3 CC| |jason at gcc dot gnu.org, | |ppalka at gcc dot gnu.org See Also| |https://gcc.gnu.org/bugzill | |a/show_bug.cgi?id=92407 Summary|Missing Destructor Call |[11/12/13 Regression] |with goto and return value |Missing Destructor Call | |with goto and return value --- Comment #1 from Patrick Palka <ppalka at gcc dot gnu.org> --- Fixed on trunk after r14-1593-g7e0b65b239c3a0, where we get the expected output Cons Dest Cons Dest and indeed this seems closely related or even a dup of PR92407 the fix for which has been backported for 11.5/12.4/13.3/14. However, using the latest 13/12/11 release branches containing the backported fix I see we now output Cons Dest Cons Dest Dest instead of Cons Cons Dest which still seems wrong? (Not sure if generating different wrong code is considered a regression..)
next prev parent reply other threads:[~2024-02-05 15:46 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 ` ppalka at gcc dot gnu.org [this message] 2024-02-05 16:37 ` [Bug c++/113767] [11/12/13 Regression] " 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-fLC4Khlm1v@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).