public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/105606] [12 Regression] std::pair with nested struct and NSDMI Date: Sun, 15 May 2022 06:44:03 +0000 [thread overview] Message-ID: <bug-105606-4-1F7jWDAW5B@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105606-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105606 --- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Note clang also rejects it for -std=c++20 and accepts it for -std=c++17. Let me dig into the changes, I suspect this is another standard change.
next prev parent reply other threads:[~2022-05-15 6:44 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-15 5:35 [Bug c++/105606] New: " mrjoel at lixil dot net 2022-05-15 6:35 ` [Bug c++/105606] " pinskia at gcc dot gnu.org 2022-05-15 6:42 ` pinskia at gcc dot gnu.org 2022-05-15 6:44 ` pinskia at gcc dot gnu.org [this message] 2022-05-15 7:00 ` [Bug c++/105606] [12 Regression] std::pair with nested struct and NSDMI and -std=c++20 mrjoel at lixil dot net 2022-05-15 7:08 ` pinskia at gcc dot gnu.org 2022-05-15 7:09 ` pinskia at gcc dot gnu.org 2023-09-27 8:39 ` cvs-commit 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-105606-4-1F7jWDAW5B@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).