public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/109172] [10/11/12/13 Regression] g++ calls a private destructor with the keyword throw after the try-block Date: Fri, 17 Mar 2023 15:05:06 +0000 [thread overview] Message-ID: <bug-109172-4-LFguEwQHB9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109172-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109172 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Given that the class is empty, my bet from those two would be on r156842. Anyway, if I add int d; before private: in #c1, it started to be accepted only in r159428 aka DR475 I think (r159421 still rejects, r159430 accepts).
next prev parent reply other threads:[~2023-03-17 15:05 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-17 11:39 [Bug c++/109172] New: " MikeSmith32564 at mail dot com 2023-03-17 11:50 ` [Bug c++/109172] " redi at gcc dot gnu.org 2023-03-17 11:57 ` [Bug c++/109172] [10/11/12/13 Regression] " redi at gcc dot gnu.org 2023-03-17 12:21 ` rguenth at gcc dot gnu.org 2023-03-17 15:05 ` jakub at gcc dot gnu.org [this message] 2023-03-17 19:28 ` jason at gcc dot gnu.org 2023-03-17 21:32 ` cvs-commit at gcc dot gnu.org 2023-03-17 21:36 ` jason at gcc dot gnu.org 2023-03-18 3:15 ` MikeSmith32564 at mail dot com 2023-03-18 9:50 ` redi at gcc dot gnu.org 2023-03-18 9:51 ` redi 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-109172-4-LFguEwQHB9@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).