public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ppalka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/105622] [13 Regression] ICE in cxx_eval_store_expression with [[no_unique_address]] and empty data members since r13-160-g967cdbe6629653 Date: Mon, 16 May 2022 19:08:20 +0000 [thread overview] Message-ID: <bug-105622-4-HqASt9Mcu0@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105622-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105622 Patrick Palka <ppalka at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Known to fail| |13.0 CC| |jason at gcc dot gnu.org Known to work| |12.1.0 Status|UNCONFIRMED |NEW Keywords| |ice-on-valid-code Ever confirmed|0 |1 Summary|ICE in |[13 Regression] ICE in |cxx_eval_store_expression |cxx_eval_store_expression |with [[no_unique_address]] |with [[no_unique_address]] |and empty data members |and empty data members | |since | |r13-160-g967cdbe6629653 Target Milestone|--- |13.0 See Also| |https://gcc.gnu.org/bugzill | |a/show_bug.cgi?id=105245 Last reconfirmed| |2022-05-16 --- Comment #1 from Patrick Palka <ppalka at gcc dot gnu.org> --- Started with r13-160-g967cdbe6629653.
next prev parent reply other threads:[~2022-05-16 19:08 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-16 19:06 [Bug c++/105622] New: ICE in cxx_eval_store_expression with [[no_unique_address]] and empty data members ppalka at gcc dot gnu.org 2022-05-16 19:08 ` ppalka at gcc dot gnu.org [this message] 2022-05-17 6:58 ` [Bug c++/105622] [13 Regression] ICE in cxx_eval_store_expression with [[no_unique_address]] since r13-160-g967cdbe6629653 rguenth at gcc dot gnu.org 2022-05-17 22:16 ` jason at gcc dot gnu.org 2022-05-24 19:50 ` cvs-commit at gcc dot gnu.org 2022-05-24 20:07 ` 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-105622-4-HqASt9Mcu0@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).