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 c/43553] libgcc built with -DHAVE_CC_TLS against xgcc when emutls in use Date: Sun, 28 Mar 2010 02:07:00 -0000 [thread overview] Message-ID: <20100328020740.18331.qmail@sourceware.org> (raw) In-Reply-To: <bug-43553-11113@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from howarth at nitro dot med dot uc dot edu 2010-03-28 02:07 ------- I based my proposed patch roughly on the orginal patch that introduced the use of -DHAVE_CC_TLS. Author: hjl Date: Fri Jul 6 14:00:46 2007 New Revision: 126416 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=126416 Log: config/ 2007-07-06 H.J. Lu <hongjiu.lu@intel.com> * tls.m4 (GCC_CHECK_CC_TLS): New. libgcc/ 2007-07-06 H.J. Lu <hongjiu.lu@intel.com> * config.host (tmake_file): Add t-tls for i[34567]86-*-linux* and x86_64-*-linux*. * config/t-tls: New file. * Makefile.in (INTERNAL_CFLAGS): Add @set_have_cc_tls@. * configure.ac: Include ../config/enable.m4 and ../config/tls.m4. Use GCC_CHECK_CC_TLS to check if assembler supports TLS and substitute set_have_cc_tls. * configure: Regenerated. libbid/ 2007-07-06 H.J. Lu <hongjiu.lu@intel.com> Updated from Intel BID library: * bid_conf.h (BID_THREAD): Defined only if both HAVE_CC_TLS and USE_TLS are defined. Added: trunk/libgcc/config/t-tls Modified: trunk/config/ChangeLog trunk/config/tls.m4 trunk/libgcc/ChangeLog trunk/libgcc/Makefile.in trunk/libgcc/config.host trunk/libgcc/config/libbid/ChangeLog trunk/libgcc/config/libbid/bid_conf.h trunk/libgcc/configure trunk/libgcc/configure.ac -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43553
next prev parent reply other threads:[~2010-03-28 2:07 UTC|newest] Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-03-28 2:03 [Bug c/43553] New: " howarth at nitro dot med dot uc dot edu 2010-03-28 2:07 ` howarth at nitro dot med dot uc dot edu [this message] 2010-03-28 2:17 ` [Bug c/43553] " howarth at nitro dot med dot uc dot edu 2010-03-28 4:39 ` howarth at nitro dot med dot uc dot edu 2010-03-28 5:49 ` howarth at nitro dot med dot uc dot edu 2010-03-28 16:11 ` howarth at nitro dot med dot uc dot edu 2010-03-28 16:29 ` howarth at nitro dot med dot uc dot edu 2010-03-28 19:21 ` howarth at nitro dot med dot uc dot edu 2010-03-28 20:31 ` howarth at nitro dot med dot uc dot edu 2010-03-28 20:59 ` howarth at nitro dot med dot uc dot edu 2010-03-30 13:09 ` rguenth at gcc dot gnu dot org 2010-03-30 16:01 ` rguenth at gcc dot gnu dot org 2010-03-31 2:17 ` howarth at nitro dot med dot uc dot edu 2010-03-31 2:44 ` howarth at nitro dot med dot uc dot edu 2010-03-31 3:54 ` howarth at nitro dot med dot uc dot edu 2010-03-31 6:15 ` howarth at nitro dot med dot uc dot edu 2010-04-01 8:02 ` developer at sandoe-acoustics dot co dot uk 2010-04-01 8:09 ` bonzini at gnu dot org 2010-04-01 8:30 ` developer at sandoe-acoustics dot co dot uk 2010-04-02 21:16 ` developer at sandoe-acoustics dot co dot uk 2010-04-02 21:32 ` developer at sandoe-acoustics dot co dot uk 2010-04-03 11:01 ` developer at sandoe-acoustics dot co dot uk 2010-04-03 20:03 ` dominiq at lps dot ens dot fr 2010-04-04 7:18 ` bonzini at gnu dot org 2010-04-04 16:30 ` howarth at nitro dot med dot uc dot edu 2010-04-04 16:33 ` howarth at nitro dot med dot uc dot edu 2010-04-04 17:59 ` howarth at nitro dot med dot uc dot edu 2010-04-04 20:19 ` developer at sandoe-acoustics dot co dot uk 2010-04-04 21:09 ` howarth at nitro dot med dot uc dot edu 2010-04-05 8:33 ` developer at sandoe-acoustics dot co dot uk 2010-05-25 12:51 ` iains at gcc dot gnu dot org 2010-05-27 15:10 ` mrs at gcc dot gnu dot org 2010-05-28 0:02 ` howarth at nitro dot med dot uc dot edu 2010-08-20 11:39 ` howarth at nitro dot med dot uc dot edu
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=20100328020740.18331.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: 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).