public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/50598] [4.7 Regression] Undefined symbols: "___emutls_v.*", ... on *-apple-darwin*
Date: Fri, 04 Nov 2011 08:57:00 -0000 [thread overview]
Message-ID: <bug-50598-4-fVuRegK2iS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50598-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50598
--- Comment #8 from Iain Sandoe <iains at gcc dot gnu.org> 2011-11-04 08:56:36 UTC ---
the following also fails (for both c and c++):
extern __thread int i;
__thread int i;
===
- producing an empty asm file
===
gcc-4.6 produces:
.globl ___emutls_v.i
.data
.align 2
___emutls_v.i:
.long 4
.long 4
.long 0
.long 0
.constructor
.destructor
.align 1
.subsections_via_symbols
====
I'm wondering if, when the variables are pruned - if they are emutls proxies,
they need to check whether the parent var is prune-able.
I looked at tree-emutls.c and it seems that the proxy variable should (in
principle) be inheriting the attributes (including external and public) of the
thread var. Perhaps they are missed in some update.
next prev parent reply other threads:[~2011-11-04 8:57 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-03 14:24 [Bug middle-end/50598] New: " dominiq at lps dot ens.fr
2011-10-04 11:05 ` [Bug middle-end/50598] " rguenth at gcc dot gnu.org
2011-10-08 20:34 ` dominiq at lps dot ens.fr
2011-10-08 21:51 ` dominiq at lps dot ens.fr
2011-10-10 13:02 ` dominiq at lps dot ens.fr
2011-10-10 15:16 ` rguenth at gcc dot gnu.org
2011-10-15 18:36 ` dominiq at lps dot ens.fr
2011-10-24 9:13 ` iains at gcc dot gnu.org
2011-10-30 17:19 ` danglin at gcc dot gnu.org
2011-11-03 18:23 ` iains at gcc dot gnu.org
2011-11-04 8:57 ` iains at gcc dot gnu.org [this message]
2011-11-04 10:52 ` iains at gcc dot gnu.org
2011-11-09 12:42 ` hubicka at gcc dot gnu.org
2011-11-10 21:03 ` iains at gcc dot gnu.org
2011-11-11 11:32 ` iains at gcc dot gnu.org
2011-11-11 12:10 ` redi at gcc dot gnu.org
2011-11-13 12:55 ` hubicka at ucw dot cz
2011-11-13 13:00 ` iains at gcc dot gnu.org
2011-11-13 13:07 ` dominiq at lps dot ens.fr
2011-11-13 14:01 ` jh at suse dot de
2011-11-14 13:13 ` hubicka at ucw dot cz
2011-11-14 16:22 ` dominiq at lps dot ens.fr
2011-11-14 16:22 ` redi at gcc dot gnu.org
2011-11-14 16:50 ` iains at gcc dot gnu.org
2011-11-14 16:56 ` howarth at nitro dot med.uc.edu
2011-11-14 17:09 ` hubicka at ucw dot cz
2011-11-14 17:57 ` hubicka at gcc dot gnu.org
2011-11-17 11:45 ` vincenzo.innocente at cern dot ch
2011-11-18 0:26 ` redi at gcc dot gnu.org
2011-11-20 12:52 ` dominiq at lps dot ens.fr
2011-11-20 13:02 ` dominiq at lps dot ens.fr
2011-11-20 14:34 ` redi at gcc dot gnu.org
2011-11-20 15:11 ` vincenzo.innocente at cern dot ch
2011-11-20 16:37 ` dominiq at lps dot ens.fr
2012-10-04 0:58 ` whatmannerofburgeristhis at gmail dot com
2012-10-04 0:58 ` whatmannerofburgeristhis at gmail dot com
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-50598-4-fVuRegK2iS@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).