public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/49316] ICE in in function_and_variable_visibility, at ipa.c:926 with g++.dg/tls/diag-1.C Date: Wed, 26 Oct 2011 09:23:00 -0000 [thread overview] Message-ID: <bug-49316-4-94juIVHyZO@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-49316-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49316 --- Comment #3 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> 2011-10-26 09:22:41 UTC --- > --- Comment #2 from Graham Reed <greed at pobox dot com> 2011-10-25 20:04:32 UTC --- > This may be the same fault I'm seeing on AIX with GCC 4.6.1--does Tru64 use an > "emulated TLS" as well? It does: while the platform could support native TLS, it is so different from the usual ELF implementations that it hasn't been implemented in gcc. > I reduced diag-1.C to this: > > template <typename T> struct B { static __thread T t; }; > template <typename T> __thread T B<T>::t = 42; > void bar () { int j = B<int>::t; } I get the same ICE on that testcase with trunk as of r180287. Rainer
next prev parent reply other threads:[~2011-10-26 9:23 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-06-07 17:42 [Bug tree-optimization/49316] New: " ro at gcc dot gnu.org 2011-07-19 14:12 ` [Bug tree-optimization/49316] " ro at gcc dot gnu.org 2011-10-25 20:04 ` greed at pobox dot com 2011-10-26 9:23 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message] 2011-10-26 15:37 ` greed at pobox dot com 2011-10-26 15:40 ` greed at pobox dot com 2011-10-26 15:52 ` ro at CeBiTec dot Uni-Bielefeld.DE 2011-10-28 17:18 ` greed at pobox dot com 2015-02-13 0:22 ` rth at gcc dot gnu.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-49316-4-94juIVHyZO@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: 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).