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/35435] New: [4.1/4.2/4.3/4.4 regression] ICE with attribute tls_model in typedef
Date: Mon, 03 Mar 2008 20:49:00 -0000 [thread overview]
Message-ID: <bug-35435-1771@http.gcc.gnu.org/bugzilla/> (raw)
The following (valid?) code snippet triggers an ICE since GCC 3.3:
==============================================================
typedef int X __attribute__((tls_model("initial-exec")));
==============================================================
bug.c:1: internal compiler error: tree check: expected var_decl, have type_decl
in handle_tls_model_attribute, at c-common.c:5936
Please submit a full bug report, [etc.]
--
Summary: [4.1/4.2/4.3/4.4 regression] ICE with attribute
tls_model in typedef
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=35435
next reply other threads:[~2008-03-03 20:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-03 20:49 reichelt at gcc dot gnu dot org [this message]
2008-03-03 20:49 ` [Bug c/35435] " reichelt at gcc dot gnu dot org
2008-03-15 1:34 ` jsm28 at gcc dot gnu dot org
2008-07-04 22:37 ` [Bug c/35435] [4.2/4.3/4.4 " jsm28 at gcc dot gnu dot org
2009-02-04 22:22 ` jsm28 at gcc dot gnu dot org
2009-02-05 1:18 ` jsm28 at gcc dot gnu dot org
2009-02-05 12:14 ` jsm28 at gcc dot gnu dot org
2009-02-05 12:18 ` [Bug c/35435] [4.2 " jsm28 at gcc dot gnu dot org
2009-03-31 15:23 ` jsm28 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-35435-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).