public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/53816] [4.7/4.8 Regression] internal compiler error: tree check: expected field_decl, have identifier_node in fixed_type_or_null, at cp/class.c:6419, with -std=c++11 option Date: Mon, 02 Jul 2012 08:56:00 -0000 [thread overview] Message-ID: <bug-53816-4-NOTBivFA6T@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53816-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53816 Richard Guenther <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |ice-checking Known to work|4.7.2 | Target Milestone|--- |4.7.2 Summary|internal compiler error: |[4.7/4.8 Regression] |tree check: expected |internal compiler error: |field_decl, have |tree check: expected |identifier_node in |field_decl, have |fixed_type_or_null, at |identifier_node in |cp/class.c:6419, with |fixed_type_or_null, at |-std=c++11 option |cp/class.c:6419, with | |-std=c++11 option Known to fail| |4.7.2 --- Comment #2 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-07-02 08:56:09 UTC --- Also fails on the 4.7 branch - but needs enabled checking. Works on the 4.6 branch.
next prev parent reply other threads:[~2012-07-02 8:56 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-06-30 6:33 [Bug c++/53816] New: " ai.azuma at gmail dot com 2012-06-30 6:34 ` [Bug c++/53816] " ai.azuma at gmail dot com 2012-07-02 8:56 ` rguenth at gcc dot gnu.org [this message] 2012-07-02 9:47 ` [Bug c++/53816] [4.7/4.8 Regression] " jakub at gcc dot gnu.org 2012-07-02 20:46 ` jason at gcc dot gnu.org 2012-07-03 3:30 ` jason at gcc dot gnu.org 2012-07-03 3:30 ` jason at gcc dot gnu.org 2012-07-03 3:31 ` jason at gcc dot gnu.org 2012-07-03 3:31 ` 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-53816-4-NOTBivFA6T@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).