public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "falk at debian dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/22028] New: ICE after invalid struct declaration Date: Sat, 11 Jun 2005 23:52:00 -0000 [thread overview] Message-ID: <20050611235210.22028.falk@debian.org> (raw) falk@juist:/tmp% cat bug.c && gcc -c bug.c int f(){ struct { int i[]; } u; } bug.c: In function 'f': bug.c:2: error: flexible array member in otherwise empty struct bug.c:2: internal compiler error: tree check: expected class 'type', have 'exceptional' (error_mark) in gimplify_type_sizes, at gimplify.c:4491 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. -- Summary: ICE after invalid struct declaration Product: gcc Version: 4.1.0 Status: UNCONFIRMED Keywords: ice-on-invalid-code, error-recovery Severity: normal Priority: P2 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: falk at debian dot org CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22028
next reply other threads:[~2005-06-11 23:52 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-06-11 23:52 falk at debian dot org [this message] 2005-06-12 0:10 ` [Bug middle-end/22028] [4.0/4.1 Regression] " pinskia at gcc dot gnu dot org 2005-06-19 20:15 ` pinskia at gcc dot gnu dot org 2005-06-19 20:16 ` pinskia at gcc dot gnu dot org 2005-06-20 14:47 ` pinskia at gcc dot gnu dot org 2005-06-26 5:24 ` cvs-commit at gcc dot gnu dot org 2005-06-26 10:33 ` steven at gcc dot gnu dot org 2005-06-26 14:34 ` [Bug middle-end/22028] [4.0 " pinskia at gcc dot gnu dot org 2005-07-08 1:45 ` mmitchel at gcc dot gnu dot org 2005-07-09 9:31 ` cvs-commit at gcc dot gnu dot org 2005-07-09 15:13 ` pinskia at gcc dot gnu dot 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=20050611235210.22028.falk@debian.org \ --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).