public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/54908] misc regressions on emutls targets remain from dynamic initialization of non-function-local TLS variables
Date: Mon, 15 Oct 2012 07:43:00 -0000 [thread overview]
Message-ID: <bug-54908-4-RqCh7jTpzp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54908-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54908
--- Comment #7 from Jason Merrill <jason at gcc dot gnu.org> 2012-10-15 07:43:16 UTC ---
(In reply to comment #5)
> Undefined symbols:
> "TLS init function for i", referenced from:
> TLS wrapper function for i in ccoTk54U.o
> __ZTH1i$non_lazy_ptr in ccoTk54U.o
> (maybe you meant: __ZTH1i$non_lazy_ptr)
The wrapper tries to use a weak reference to the init function so that if the
variable doesn't need dynamic initialization it can just omit the init function
so the wrapper won't call it. This seems to not be working on darwin, but I
thought darwin had weakrefs?
next prev parent reply other threads:[~2012-10-15 7:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-12 13:02 [Bug target/54908] New: " howarth at nitro dot med.uc.edu
2012-10-12 13:22 ` [Bug target/54908] " howarth at nitro dot med.uc.edu
2012-10-12 15:44 ` howarth at nitro dot med.uc.edu
2012-10-12 15:49 ` howarth at nitro dot med.uc.edu
2012-10-12 18:38 ` jason at gcc dot gnu.org
2012-10-12 18:51 ` dominiq at lps dot ens.fr
2012-10-15 7:32 ` jason at gcc dot gnu.org
2012-10-15 7:43 ` jason at gcc dot gnu.org [this message]
2012-10-15 14:08 ` howarth at nitro dot med.uc.edu
2012-10-15 14:24 ` howarth at nitro dot med.uc.edu
2012-10-16 15:51 ` howarth at nitro dot med.uc.edu
2012-12-15 4:16 ` [Bug target/54908] [4.8 regression] " jason at gcc dot gnu.org
2013-01-19 5:25 ` jason at gcc dot gnu.org
2013-02-01 17:53 ` jason 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-54908-4-RqCh7jTpzp@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).