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/109113] [10/11/12/13 Regression] internal compiler error: in output_constructor_regular_field, at varasm.cc:5521 Date: Wed, 15 Mar 2023 13:45:34 +0000 [thread overview] Message-ID: <bug-109113-4-ReVjX7lkjb@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109113-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109113 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Started with my r8-6028-gb4923738ef57a441f6f9 struct A { int a; }; struct B { int b; struct A c[]; }; struct C { int d; struct B e[]; }; const struct B f = { .c = { 1 } }; struct C g = { .e = { f } }; struct C h = { .e = { f, f } }; The question is if we want to accept the g initializer and reject just the h one, or reject both. g compiles fine though and could be useful...
next prev parent reply other threads:[~2023-03-15 13:45 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-13 19:57 [Bug c/109113] New: " noe.lopez at epitech dot eu 2023-03-13 19:59 ` [Bug c/109113] " noe.lopez at epitech dot eu 2023-03-13 19:59 ` noe.lopez at epitech dot eu 2023-03-13 20:01 ` pinskia at gcc dot gnu.org 2023-03-13 20:06 ` pinskia at gcc dot gnu.org 2023-03-13 22:04 ` noe.lopez at epitech dot eu 2023-03-14 8:10 ` [Bug c/109113] [10/11/12/13 Regression] " rguenth at gcc dot gnu.org 2023-03-15 13:45 ` jakub at gcc dot gnu.org [this message] 2023-03-15 14:02 ` jakub at gcc dot gnu.org 2023-03-15 19:09 ` jakub at gcc dot gnu.org 2023-03-15 19:14 ` jakub at gcc dot gnu.org 2023-07-07 10:45 ` [Bug c/109113] [11/12/13/14 " 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-109113-4-ReVjX7lkjb@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).