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 libstdc++/52104] go1 fails to link on Solaris 8/9 x86 with native TLS
Date: Fri, 03 Feb 2012 10:21:00 -0000 [thread overview]
Message-ID: <bug-52104-4-VOW9uphDYk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52104-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52104
--- Comment #4 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> 2012-02-03 10:21:03 UTC ---
> --- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-02-03 10:11:40 UTC ---
> Looks as though we need an extra explicit instantiation in src/c++11/future.cc
Seems so. This would most likely also resolve a bootstrap failure I'm
seeing on Solaris 10 and 11/x86 with the gas/gld combo:
go1 fails to run with
ld.so.1: go1: fatal: relocation error: R_386_UNKNOWN37: file
/var/gcc/regression/trunk/10-gcc-gas-gld/build/gcc/go1: symbol
_ZSt15__once_callable: offset size (0 bytes) is not supported
gccgo: internal compiler error: Killed (program go1)
That R_386_UNKNOWN37 relocation is R_386_TLS_TPOFF32, not supported even
on Solaris 11. If I look at the previous (20120127) libstdc++.a (go1 is
linked with -static-libstdc++), I find:
> nm -A libstdc++.a |grep once_callable
libstdc++.a[mutex.o]: [29] | 0| 4|TLS |GLOB |0 |8
|_ZSt15__once_callable
As of 20120202, I get this instead:
libstdc++.a[mutex.o]: [29] | 0| 4|TLS |GLOB |0 |8
|_ZSt15__once_callable
libstdc++.a[future.o]: [144] | 0| 0|TLS |GLOB |0 |UNDEF
|_ZSt15__once_callable
Seems to be the same issue.
Rainer
next prev parent reply other threads:[~2012-02-03 10:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 10:04 [Bug libstdc++/52104] New: " ro at gcc dot gnu.org
2012-02-03 10:05 ` [Bug libstdc++/52104] " ro at gcc dot gnu.org
2012-02-03 10:06 ` ro at gcc dot gnu.org
2012-02-03 10:12 ` redi at gcc dot gnu.org
2012-02-03 10:21 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message]
2012-02-03 10:48 ` redi at gcc dot gnu.org
2012-02-03 10:56 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-02-03 11:09 ` redi at gcc dot gnu.org
2012-02-03 13:09 ` ro at gcc dot gnu.org
2012-02-05 18:40 ` ebotcazou at gcc dot gnu.org
2012-02-05 19:17 ` redi at gcc dot gnu.org
2012-02-05 23:27 ` ebotcazou at gcc dot gnu.org
2012-02-05 23:57 ` redi at gcc dot gnu.org
2012-02-06 21:37 ` redi at gcc dot gnu.org
2012-02-10 15:23 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-03-09 16:16 ` [Bug libstdc++/52104] go1 fails to run on Solaris 10/11 x86 with with gld ro at gcc dot gnu.org
2012-03-22 8:55 ` rguenth at gcc dot gnu.org
2012-07-02 12:57 ` rguenth 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-52104-4-VOW9uphDYk@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).