public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cas43 at cs dot stanford.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/52290] New: internal compiler error: tree check: expected function_decl, have var_decl in start_function, at c-decl.c:7712
Date: Thu, 16 Feb 2012 23:51:00 -0000	[thread overview]
Message-ID: <bug-52290-4@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52290

             Bug #: 52290
           Summary: internal compiler error: tree check: expected
                    function_decl, have var_decl in start_function, at
                    c-decl.c:7712
    Classification: Unclassified
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: cas43@cs.stanford.edu


Triggered by the (invalid) C source:
int f()[j]

Diagnostic:
2.c:1:9: error: ‘j’ undeclared here (not in a function)
2.c:1:1: internal compiler error: tree check: expected function_decl, have
var_decl in start_function, at c-decl.c:7712
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.

Compiler version:
Using built-in specs.
COLLECT_GCC=/new-gcc/i-4.7/bin/gcc
COLLECT_LTO_WRAPPER=/new-gcc/i-4.7/libexec/gcc/x86_64-unknown-linux-gnu/4.7.0/lto-wrapper
Target: x86_64-unknown-linux-gnu
Configured with: ../s-4.7/configure --prefix=/new-gcc/i-4.7
Thread model: posix
gcc version 4.7.0 20120216 (experimental) (GCC)


             reply	other threads:[~2012-02-16 23:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-16 23:51 cas43 at cs dot stanford.edu [this message]
2012-02-20 12:24 ` [Bug c/52290] [4.4/4.5/4.6/4.7 Regression] " rguenth at gcc dot gnu.org
2012-02-22 10:11 ` 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@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).