public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "law at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/112301] [12/13/14 regression] Double destruction of returned object when exiting the scope causes an exception which gets rethrown since r12-6333-gb10e031458d541 Date: Mon, 04 Mar 2024 04:26:43 +0000 [thread overview] Message-ID: <bug-112301-4-JT9HQCzFP9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112301-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112301 Jeffrey A. Law <law at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |law at gcc dot gnu.org Resolution|--- |FIXED Status|ASSIGNED |RESOLVED --- Comment #9 from Jeffrey A. Law <law at gcc dot gnu.org> --- Jason fixed this and backported the fix to the gcc-12 and gcc-13 branches.
prev parent reply other threads:[~2024-03-04 4:26 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-30 16:14 [Bug c++/112301] New: Double destruction of returned object when exiting the scope causes an exception which gets rethrown alexander.grund@tu-dresden.de 2023-10-30 16:29 ` [Bug c++/112301] [Regression 12/13/14] " redi at gcc dot gnu.org 2023-10-30 21:45 ` jason at gcc dot gnu.org 2023-11-02 20:01 ` [Bug c++/112301] [12/13/14 regression] Double destruction of returned object when exiting the scope causes an exception which gets rethrown since r12-6333-gb10e031458d541 cvs-commit at gcc dot gnu.org 2023-11-02 20:03 ` jason at gcc dot gnu.org 2023-11-03 10:01 ` alexander.grund@tu-dresden.de 2023-11-17 0:21 ` cvs-commit at gcc dot gnu.org 2023-11-17 0:21 ` cvs-commit at gcc dot gnu.org 2024-01-12 8:27 ` rguenth at gcc dot gnu.org 2024-01-12 8:32 ` pinskia at gcc dot gnu.org 2024-03-04 4:26 ` law 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-112301-4-JT9HQCzFP9@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).