public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "howarth at nitro dot med dot uc dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/43602] ___emutls_v.__gcov_indirect_call_[counters|callee] undefined on *-*-darwin*
Date: Wed, 31 Mar 2010 13:30:00 -0000 [thread overview]
Message-ID: <20100331132954.24222.qmail@sourceware.org> (raw)
In-Reply-To: <bug-43602-11113@http.gcc.gnu.org/bugzilla/>
------- Comment #1 from howarth at nitro dot med dot uc dot edu 2010-03-31 13:29 -------
The commit of the patch to eliminate race conditions in indirect value
profiling (r157822) hasn't triggered the same profile related testsuite
failures in any other target. This leads to two questions...
1) Does any other target really use emulated tls besides darwin?
2) Is standard tls the same as native tls? In other words, are there really
three forms, (tls, native tls and emulated tls, or just two forms (native) tls
and emulated tls?
I ask because according to...
case ${host} in
i[34567]86-*-linux* | x86_64-*-linux* | \
i[34567]86-*-kfreebsd*-gnu | i[34567]86-*-knetbsd*-gnu | \
i[34567]86-*-gnu*)
tmake_file="${tmake_file} t-tls"
;;
esac
...only those targets are using native tls which would suggest (if there are
only two forms of tls) that targets like powerpc64-*-linux* should be using
emulated tls like darwin and thus be failing the profile testcases now. This
isn't the case.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43602
next prev parent reply other threads:[~2010-03-31 13:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-31 13:22 [Bug middle-end/43602] New: " howarth at nitro dot med dot uc dot edu
2010-03-31 13:30 ` howarth at nitro dot med dot uc dot edu [this message]
2010-03-31 13:42 ` [Bug middle-end/43602] " howarth at nitro dot med dot uc dot edu
2010-03-31 14:53 ` howarth at nitro dot med dot uc dot edu
2010-03-31 15:19 ` howarth at nitro dot med dot uc dot edu
2010-03-31 15:23 ` howarth at nitro dot med dot uc dot edu
2010-03-31 20:21 ` howarth at nitro dot med dot uc dot edu
2010-03-31 20:40 ` dominiq at lps dot ens dot fr
2010-03-31 20:55 ` dominiq at lps dot ens dot fr
2010-03-31 21:05 ` howarth at nitro dot med dot uc dot edu
2010-03-31 23:30 ` howarth at nitro dot med dot uc dot edu
2010-03-31 23:52 ` howarth at nitro dot med dot uc dot edu
2010-04-01 0:55 ` [Bug middle-end/43602] New: " Auser99
2010-04-01 5:12 ` [Bug middle-end/43602] " howarth at nitro dot med dot uc dot edu
2010-04-01 5:13 ` howarth at nitro dot med dot uc dot edu
2010-04-01 11:28 ` howarth at nitro dot med dot uc dot edu
2010-04-01 13:25 ` rguenth at gcc dot gnu dot org
2010-04-01 13:26 ` rguenth at gcc dot gnu dot org
2010-04-01 15:42 ` bonzini at gnu dot org
2010-04-01 16:00 ` howarth at nitro dot med dot uc dot edu
2010-04-01 16:01 ` bonzini at gnu dot org
2010-04-05 8:32 ` developer at sandoe-acoustics dot co dot uk
2010-05-15 15:40 ` iains at gcc dot gnu dot org
2010-05-19 14:54 ` iains at gcc dot gnu dot org
2010-05-24 14:37 ` iains at gcc dot gnu dot 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=20100331132954.24222.qmail@sourceware.org \
--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).