public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "belyshev at lubercy dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/16046] New: ICE tree check: expected tree_list, have identifier_node in decl_attributes, at attribs.c:151 Date: Fri, 18 Jun 2004 05:10:00 -0000 [thread overview] Message-ID: <20040618051016.16046.belyshev@lubercy.com> (raw) bug.c: ---------------------------------------------- __attribute__((foo) int f (){} ---------------------------------------------- ^ note: ')' missing ./cc1 bug.c -quiet -o /dev/null bug.c:1: error: syntax error before "int" bug.c:1: internal compiler error: tree check: expected tree_list, have identifier_node in decl_attributes, at attribs.c:151 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. -- Summary: ICE tree check: expected tree_list, have identifier_node in decl_attributes, at attribs.c:151 Product: gcc Version: 3.5.0 Status: UNCONFIRMED Keywords: ice-on-invalid-code Severity: normal Priority: P2 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: belyshev at lubercy dot com CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16046
next reply other threads:[~2004-06-18 5:10 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-06-18 5:10 belyshev at lubercy dot com [this message] 2004-06-18 5:18 ` [Bug c/16046] [3.5? Regression] " pinskia at gcc dot gnu dot org 2004-06-18 5:38 ` [Bug c/16046] [3.5 " belyshev at lubercy dot com 2004-06-18 5:40 ` belyshev at lubercy dot com 2004-07-17 4:00 ` pinskia at gcc dot gnu dot org 2004-08-13 11:50 ` reichelt at gcc dot gnu dot org 2004-08-13 15:22 ` echristo at redhat dot com 2004-09-10 0:31 ` echristo at redhat dot com 2004-09-11 0:00 ` cvs-commit at gcc dot gnu dot org 2004-09-11 1:17 ` [Bug c/16046] [4.0 " pinskia at gcc dot gnu dot 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=20040618051016.16046.belyshev@lubercy.com \ --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).