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 target/49541] [4.6/4.7 regression] TLS support partially broken in 64-bit mode
Date: Wed, 06 Jul 2011 14:07:00 -0000 [thread overview]
Message-ID: <bug-49541-4-eUvs3yU7xk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49541-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49541
--- Comment #2 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> 2011-07-06 14:06:59 UTC ---
> --- Comment #1 from Eric Botcazou <ebotcazou at gcc dot gnu.org> 2011-07-06 08:52:17 UTC ---
> Rainer, any idea to solve this?
One comment up front: It's best to directly Cc: me in PRs, otherwise I
may easily miss them.
It took me some time to understand why this didn't hit me in my S8
bootstraps, but they run in an S8 branded zone, where the alternate
thread library is copied over the default one, so __tls_get_addr is also
found in /lib/sparcv9/libthread.so.
Trying on our only native S8 machine, I see the same failure.
I think the only solution is to move LIB_THREAD_LDFLAGS_SPEC out of
LIB_SPEC (which is way too late, as you've observed) and into or in
front of LINK_ARCH_SPEC where all the other -L/-R flags are passed.
I'll have a look at this.
Rainer
next prev parent reply other threads:[~2011-07-06 14:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 9:05 [Bug target/49541] New: " ebotcazou at gcc dot gnu.org
2011-06-27 9:49 ` [Bug target/49541] " rguenth at gcc dot gnu.org
2011-07-06 8:53 ` ebotcazou at gcc dot gnu.org
2011-07-06 14:07 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message]
2011-07-13 9:21 ` ro at gcc dot gnu.org
2011-07-13 16:12 ` ebotcazou at gcc dot gnu.org
2011-07-13 17:57 ` ro at CeBiTec dot Uni-Bielefeld.DE
2011-07-13 17:59 ` ro at gcc dot gnu.org
2011-07-13 19:35 ` ebotcazou at gcc dot gnu.org
2011-07-14 17:09 ` ro at CeBiTec dot Uni-Bielefeld.DE
2011-07-14 17:38 ` ro at gcc dot gnu.org
2011-07-14 17:40 ` ro at gcc dot gnu.org
2011-07-15 9:34 ` ebotcazou at gcc dot gnu.org
2011-07-15 9:34 ` ebotcazou at gcc dot gnu.org
2011-07-15 9:40 ` ro at gcc dot gnu.org
2011-07-15 12:01 ` ro at CeBiTec dot Uni-Bielefeld.DE
2011-07-15 12:05 ` ro at gcc dot gnu.org
2011-07-18 12:10 ` ro at gcc dot gnu.org
2011-07-18 12:11 ` ro at gcc dot gnu.org
2011-07-18 12:15 ` ro 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-49541-4-eUvs3yU7xk@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).