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++/101767] [10/11/12 Regression] Aggregate initialization fails for struct that has both unnamed struct and union fields Date: Tue, 03 Aug 2021 20:50:42 +0000 [thread overview] Message-ID: <bug-101767-4-a0J1t0JqQT@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101767-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101767 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[11/12 Regression] |[10/11/12 Regression] |Aggregate initialization |Aggregate initialization |fails for struct that has |fails for struct that has |both unnamed struct and |both unnamed struct and |union fields |union fields Target Milestone|11.3 |10.4 See Also| |https://gcc.gnu.org/bugzill | |a/show_bug.cgi?id=100489 Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Known to work| |10.3.0 Last reconfirmed| |2021-08-03 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- So this is most likely caused by the patch which fixes PR 100489 so this is a regression in 10.4.0 also.
next prev parent reply other threads:[~2021-08-03 20:50 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-03 20:18 [Bug c++/101767] New: " xtkoba at gmail dot com 2021-08-03 20:40 ` [Bug c++/101767] [11/12 Regression] " pinskia at gcc dot gnu.org 2021-08-03 20:50 ` pinskia at gcc dot gnu.org [this message] 2021-08-04 5:59 ` [Bug c++/101767] [10/11/12 " rguenth at gcc dot gnu.org 2021-11-16 21:56 ` pinskia at gcc dot gnu.org 2022-01-20 14:52 ` ppalka at gcc dot gnu.org 2022-02-09 8:23 ` antmak.pub at gmail dot com 2022-03-18 18:12 ` jason at gcc dot gnu.org 2022-03-21 20:47 ` cvs-commit at gcc dot gnu.org 2022-03-21 20:58 ` [Bug c++/101767] [11 " jason at gcc dot gnu.org 2022-03-22 5:18 ` cvs-commit at gcc dot gnu.org 2022-03-26 23:29 ` jason at gcc dot gnu.org 2022-05-12 21:14 ` cvs-commit at gcc dot gnu.org 2022-05-12 22:24 ` 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-101767-4-a0J1t0JqQT@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).