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++/98994] [11 Regression] Empty type with [[no_unique_address]] in union with constructor is not a constant expression since r11-6918 Date: Mon, 08 Feb 2021 09:40:02 +0000 [thread overview] Message-ID: <bug-98994-4-C8DBWu69vG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98994-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98994 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Priority|P3 |P1 Summary|[11 Regression] Empty type |[11 Regression] Empty type |with [[no_unique_address]] |with [[no_unique_address]] |in union with constructor |in union with constructor |is not a constant |is not a constant |expression |expression since r11-6918 Last reconfirmed| |2021-02-08 Ever confirmed|0 |1 CC| |jakub at gcc dot gnu.org, | |jason at gcc dot gnu.org --- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Started with r11-6918-ga4dfd0f089af33f2af57bf422f9859405b9b4a16
next prev parent reply other threads:[~2021-02-08 9:40 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-08 0:10 [Bug c++/98994] New: Empty type with [[no_unique_address]] in union with constructor is not a constant expression david at doublewise dot net 2021-02-08 9:35 ` [Bug c++/98994] [11 Regression] " rguenth at gcc dot gnu.org 2021-02-08 9:40 ` jakub at gcc dot gnu.org [this message] 2021-02-08 20:41 ` [Bug c++/98994] [11 Regression] Empty type with [[no_unique_address]] in union with constructor is not a constant expression since r11-6918 jason at gcc dot gnu.org 2021-02-09 1:52 ` cvs-commit at gcc dot gnu.org 2021-02-09 14:35 ` jason 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-98994-4-C8DBWu69vG@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).