public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jens.maurer at gmx dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/106812] New: Throwing a non-copyable exception Date: Fri, 02 Sep 2022 07:14:15 +0000 [thread overview] Message-ID: <bug-106812-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106812 Bug ID: 106812 Summary: Throwing a non-copyable exception Product: gcc Version: 12.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: jens.maurer at gmx dot net Target Milestone: --- gcc accepts the following program: struct S { S() = default; S(const S&) = delete; // int x = 0; // #3 }; int main() { try { throw S(); // #1 } catch (S s) { // #2 return 1; } } but it is ill-formed at #1 according to [except.throw] p5. Curiously, if line #3 is added, gcc flags an error at #2 (but not at #1).
next reply other threads:[~2022-09-02 7:14 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-02 7:14 jens.maurer at gmx dot net [this message] 2022-09-02 7:21 ` [Bug c++/106812] " jens.maurer at gmx dot net 2022-09-19 18:53 ` mpolacek at gcc dot gnu.org 2022-09-19 19:01 ` mpolacek at gcc dot gnu.org 2022-10-14 18:18 ` chgros at coverity dot com
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-106812-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: 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).