public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "reichelt at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/37645] New: [4.2/4.3/4.4 regression] ICE with weakref attribute
Date: Thu, 25 Sep 2008 06:54:00 -0000 [thread overview]
Message-ID: <bug-37645-1771@http.gcc.gnu.org/bugzilla/> (raw)
The following code snippet triggers an ICE since GCC 4.1.0:
==========================================================
void foo(int i __attribute__((__weakref__ ("xyz"))));
==========================================================
bug.c:1: internal compiler error: tree check: expected tree that contains 'decl
with visibility' structure, have 'parm_decl' in handle_weakref_attribute, at
c-common.c:6162
Please submit a full bug report, [etc.]
Before GCC 4.1.0 the code was accepted with the following warning:
bug.c:1: warning: '__weakref__' attribute directive ignored
--
Summary: [4.2/4.3/4.4 regression] ICE with weakref attribute
Product: gcc
Version: 4.4.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code, monitored
Severity: normal
Priority: P3
Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: reichelt at gcc dot gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37645
next reply other threads:[~2008-09-25 6:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-25 6:54 reichelt at gcc dot gnu dot org [this message]
2008-09-25 6:55 ` [Bug c/37645] " reichelt at gcc dot gnu dot org
2008-09-25 14:38 ` jakub at gcc dot gnu dot org
2008-09-26 5:12 ` jakub at gcc dot gnu dot org
2008-09-26 5:26 ` jakub at gcc dot gnu dot org
2008-09-26 5:28 ` jakub 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=bug-37645-1771@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).