public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "uros 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: Thu, 23 Feb 2012 18:05:00 -0000	[thread overview]
Message-ID: <bug-52290-4-tFWiWPtuhK@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

--- Comment #6 from uros at gcc dot gnu.org 2012-02-23 18:03:47 UTC ---
Author: uros
Date: Thu Feb 23 18:03:33 2012
New Revision: 184518

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=184518
Log:
    PR c/52290
    * c-decl.c (start_function): Exit early if decl1 is not FUNTION_DECL.

testsuite/ChangeLog:

    PR c/52290
    * gcc.dg/noncompile/pr52290.c: New test.


Added:
    branches/gcc-4_4-branch/gcc/testsuite/gcc.dg/noncompile/pr52290.c
      - copied unchanged from r184511,
trunk/gcc/testsuite/gcc.dg/noncompile/pr52290.c
Modified:
    branches/gcc-4_4-branch/gcc/ChangeLog
    branches/gcc-4_4-branch/gcc/c-decl.c
    branches/gcc-4_4-branch/gcc/testsuite/ChangeLog


  parent reply	other threads:[~2012-02-23 18:05 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 ` [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 [this message]
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-tFWiWPtuhK@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).