public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug gcov-profile/58127] [4.9 Regression] 37 failures in gcc.dg/tree-prof/ for x86_64-apple-darwin10 Date: Sat, 17 Aug 2013 20:09:00 -0000 [thread overview] Message-ID: <bug-58127-4-MheMtP7EIx@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-58127-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58127 Jan Hubicka <hubicka at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #4 from Jan Hubicka <hubicka at gcc dot gnu.org> --- The secret plan was to not use TLS for emutls. I did not introduce new use of TLS, just use what was already in tree-profile.c: if (targetm.have_tls) DECL_TLS_MODEL (ic_void_ptr_var) = decl_default_tls_model (ic_void_ptr_var); and I think have_tls should be true only for non-emutls targets. on libgcov time we use #ifdef HAVE_CC_TLS __thread #endif There seems to be macro USE_EMUTLS specifying if we have real TLS or emuTLS. I am not sure what of the two tests passes. Perhaps it will help to replace #ifdef HAVE_CC_TLS __thread #endif #if defined(HAVE_CC_TLS) && !defined (USE_EMUTLS) __thread #endif
next prev parent reply other threads:[~2013-08-17 20:09 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-08-11 17:16 [Bug gcov-profile/58127] New: " dominiq at lps dot ens.fr 2013-08-12 8:42 ` [Bug gcov-profile/58127] " dominiq at lps dot ens.fr 2013-08-17 8:22 ` iains at gcc dot gnu.org 2013-08-17 10:43 ` iains at gcc dot gnu.org 2013-08-17 20:09 ` hubicka at gcc dot gnu.org [this message] 2013-08-17 20:24 ` iains at gcc dot gnu.org 2013-08-18 12:27 ` iains at gcc dot gnu.org 2013-08-18 13:10 ` hubicka at ucw dot cz 2013-08-18 13:50 ` dominiq at lps dot ens.fr 2013-08-18 16:07 ` iains at gcc dot gnu.org 2013-08-18 16:07 ` iains at gcc dot gnu.org 2013-08-18 16:10 ` dominiq at lps dot ens.fr
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-58127-4-MheMtP7EIx@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: linkBe 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).