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, 13 Jul 2011 17:57:00 -0000 [thread overview]
Message-ID: <bug-49541-4-szVLJi4AFl@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 #5 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> 2011-07-13 17:56:26 UTC ---
> --- Comment #4 from Eric Botcazou <ebotcazou at gcc dot gnu.org> 2011-07-13 16:11:25 UTC ---
>> Since I could only run the bootstrap on a Solaris 8 branded zone where the
>> default libthread.so is a copy of the lwp one, could you try it on bare metal
>> to confirm that it works?
>
> Works essentially OK by me. The only remaining glitches are:
Fine, I'll commit the patch then.
> output is:
> Undefined first referenced
> symbol in file
> __tls_get_addr
> /nile.build/botcazou/gcc-head/sparc-sun-solaris2.8/sparc-sun-solaris2.8/sparcv9/libgomp/.libs/libgomp.so
> ld: fatal: Symbol referencing errors. No output written to ./condinc2.exe
> collect2: error: ld returned 1 exit status
>
> FAIL: libgomp.fortran/condinc2.f -O (test for excess errors
>
>
> but this is more of a test harness issue: the 4 tests are compiled with the
> combination -fno-openmp -lgomp so -pthread isn't added by the driver.
This is strange: in my case, libgomp.so is self-contained and linked
with the right libthread.so which provides __tls_get_addr:
> LD_LIBRARY_PATH=. ldd -r ./libgomp.so.1
librt.so.1 => /usr/lib/64/librt.so.1
libgcc_s.so.1 => ./libgcc_s.so.1
libpthread.so.1 => /usr/lib/64/libpthread.so.1
libthread.so.1 => /usr/lib/lwp/64/libthread.so.1
libc.so.1 => /usr/lib/64/libc.so.1
libaio.so.1 => /usr/lib/64/libaio.so.1
libdl.so.1 => /usr/lib/64/libdl.so.1
/usr/platform/SUNW,Sun-Fire-V440/lib/sparcv9/libc_psr.so.1
Rainer
next prev parent reply other threads:[~2011-07-13 17:57 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
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 [this message]
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-szVLJi4AFl@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).