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/52290] [4.4/4.5/4.6/4.7 Regression] internal compiler error: tree check: expected function_decl, have var_decl in start_function, at c-decl.c:7712 Date: Mon, 20 Feb 2012 12:24:00 -0000 [thread overview] Message-ID: <bug-52290-4-NAv8jYkjsV@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-52290-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52290 Richard Guenther <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Known to work| |4.0.4 Keywords| |error-recovery, | |ice-on-invalid-code Last reconfirmed| |2012-02-20 Ever Confirmed|0 |1 Summary|internal compiler error: |[4.4/4.5/4.6/4.7 |tree check: expected |Regression] internal |function_decl, have |compiler error: tree check: |var_decl in start_function, |expected function_decl, |at c-decl.c:7712 |have var_decl in | |start_function, at | |c-decl.c:7712 Target Milestone|--- |4.4.7 Known to fail| |4.1.0 --- Comment #1 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-02-20 12:17:27 UTC --- Confirmed. Regression from 4.0.
next prev parent reply other threads:[~2012-02-20 12:20 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-16 23:51 [Bug c/52290] New: " cas43 at cs dot stanford.edu 2012-02-20 12:24 ` rguenth at gcc dot gnu.org [this message] 2012-02-22 10:11 ` [Bug c/52290] [4.4/4.5/4.6/4.7 Regression] " jakub at gcc dot gnu.org 2012-02-22 23:38 ` ubizjak at gmail dot com 2012-02-23 16:42 ` uros at gcc dot gnu.org 2012-02-23 17:43 ` uros at gcc dot gnu.org 2012-02-23 18:04 ` uros at gcc dot gnu.org 2012-02-23 18:05 ` uros at gcc dot gnu.org 2012-02-23 18:07 ` ubizjak at gmail dot com
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-52290-4-NAv8jYkjsV@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).