public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cnstar9988 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/37308] bootstrap hangs in libstdc++
Date: Mon, 01 Sep 2008 11:26:00 -0000	[thread overview]
Message-ID: <20080901112447.25098.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37308-14862@http.gcc.gnu.org/bugzilla/>



------- Comment #8 from cnstar9988 at gmail dot com  2008-09-01 11:24 -------
When I remove TLS check code in libstdc++-v3/configure, bootstrap OK!!!

Does there have anything harm when remove the TLS check code? affect only C++?
Thanks!
==================================================================
  # For TLS support.  

enable_tls=no
gcc_cv_have_tls=no

  # For _Unwind_GetIPInfo.


======================================================
conftest.c
===============
__thread int a,b;
int main()
{
  return a==b;
}


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37308


  parent reply	other threads:[~2008-09-01 11:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-01  5:40 [Bug bootstrap/37308] New: bootstrap hug on libstdc++.a cnstar9988 at gmail dot com
2008-09-01  9:54 ` [Bug bootstrap/37308] " paolo dot carlini at oracle dot com
2008-09-01 10:16 ` cnstar9988 at gmail dot com
2008-09-01 10:24 ` cnstar9988 at gmail dot com
2008-09-01 10:26 ` [Bug bootstrap/37308] bootstrap hangs in libstdc++ paolo dot carlini at oracle dot com
2008-09-01 10:43   ` Andrew Thomas Pinski
2008-09-01 10:35 ` cnstar9988 at gmail dot com
2008-09-01 10:45 ` pinskia at gmail dot com
2008-09-01 11:11 ` paolo dot carlini at oracle dot com
2008-09-01 11:26 ` cnstar9988 at gmail dot com [this message]
2008-09-02 20:17 ` dje at gcc dot gnu dot org
     [not found] <bug-37308-4@http.gcc.gnu.org/bugzilla/>
2012-01-28  4:59 ` pinskia at gcc dot gnu.org
2012-05-22  7:21 ` pinskia 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=20080901112447.25098.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).