public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fchelnokov at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/101500] New: gcc accepts the code with extra curly braces Date: Sun, 18 Jul 2021 21:28:52 +0000 [thread overview] Message-ID: <bug-101500-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101500 Bug ID: 101500 Summary: gcc accepts the code with extra curly braces Product: gcc Version: 11.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: fchelnokov at gmail dot com Target Milestone: --- The following ill-formed code is the illustration ``` struct A { A() {} A( A&& ) = delete; ~A() {} }; int main() { const A a = {{A{}}}; //error line } ``` https://gcc.godbolt.org/z/eq5WhTfz3
next reply other threads:[~2021-07-18 21:28 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-18 21:28 fchelnokov at gmail dot com [this message] 2021-07-19 10:36 ` [Bug c++/101500] [9/10/11/12 Regression] " redi at gcc dot gnu.org 2021-07-19 11:50 ` rguenth at gcc dot gnu.org 2022-01-20 12:43 ` rguenth at gcc dot gnu.org 2022-04-15 15:44 ` [Bug c++/101500] [C++17] [DR2311] " jason at gcc dot gnu.org 2022-05-27 9:06 ` rguenth 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-101500-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).