public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/64768] [4.8/4.9/5 Regression] internal compiler error: tree check: expected tree that contains ‘decl with RTL’ structure, have ‘field_decl’ in set_decl_rtl, at emit-rtl.c:1274
Date: Sat, 24 Jan 2015 18:18:00 -0000 [thread overview]
Message-ID: <bug-64768-4-EzKrENa0GH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64768-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64768
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|ice-on-invalid-code |ice-on-valid-code,
| |rejects-valid
--- Comment #7 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
(In reply to joseph@codesourcery.com from comment #6)
> On Sat, 24 Jan 2015, mpolacek at gcc dot gnu.org wrote:
>
> > typedef int A[];
> > struct { int i; A a; } a;
>
> This is valid code for C99 and above / gnu89 (i.e., it's valid to use a
> typedef when declaring a flexible array member, whenever flexible array
> members are accepted).
Yeah, initially I had the invalid testcase as in #c0, only then I discovered
that we ICE even on a valid testcase with a typedef. Which means there are two
issues: a) we ICE, b) we don't accept a code where a flexible array member is a
typedef. I'm adjusting the keywords now.
next prev parent reply other threads:[~2015-01-24 18:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-24 10:27 [Bug c/64768] New: " mpolacek at gcc dot gnu.org
2015-01-24 10:30 ` [Bug c/64768] [4.8/4.9/5 Regression] " mpolacek at gcc dot gnu.org
2015-01-24 10:39 ` mpolacek at gcc dot gnu.org
2015-01-24 10:46 ` mpolacek at gcc dot gnu.org
2015-01-24 11:51 ` jakub at gcc dot gnu.org
2015-01-24 18:18 ` mpolacek at gcc dot gnu.org [this message]
2015-01-26 11:31 ` rguenth at gcc dot gnu.org
2015-02-14 11:25 ` mpolacek at gcc dot gnu.org
2015-02-14 11:30 ` mpolacek 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-64768-4-EzKrENa0GH@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: link
Be 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).