From: hjl@lucon.org (H.J. Lu)
To: jason@cygnus.com (Jason Merrill)
Cc: egcs@cygnus.com, drepper@cygnus.com
Subject: Re: A STL patch for egcs 1.0.2
Date: Thu, 19 Feb 1998 10:47:00 -0000 [thread overview]
Message-ID: <m0y5azh-00058fC@ocean.lucon.org> (raw)
In-Reply-To: <u9yaz7jwip.fsf@yorick.cygnus.com>
>
> >>>>> H J Lu <hjl@lucon.org> writes:
>
> > Ulrich, this will make STL thread-safe for glibc 2 and at the same
> > time, the non-thread code should be ok. Can you take a look? libstdc++
> > in egcs 1.0.2 should be fixed for glibc 2.
>
> I still think not enough people are writing threaded code to make this
It is kind of saying noone uses namespace with g++. Yes, they are
people using thread with glibc 2. Yes, some of them use C++. I don't
think making libstdc++ thread-unsafe is acceptable for glibc 2. BTW,
my change only affects glibc 2. The rest remains the same.
> necessary for 1.0.2. Also, your patch changes more than necessary; there's
> no need to add #includes of stl_config.h.
>
STL needs a way to find the system is based on glibc 2 so that
thread is enabled for glibc 2 automatically. Do you have any
suggestions?
--
H.J. Lu (hjl@gnu.org)
next prev parent reply other threads:[~1998-02-19 10:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-02-17 9:51 (1.0.2) std/bastring.h change -- Why add std/bastring.cc? Mumit Khan
1998-02-17 10:40 ` Joe Buck
[not found] ` <199802171840.KAA06006.cygnus.egcs@atrus.synopsys.com>
1998-02-17 13:54 ` Jason Merrill
1998-02-17 15:16 ` H.J. Lu
1998-02-17 23:59 ` Mumit Khan
1998-02-18 14:54 ` H.J. Lu
1998-02-18 14:54 ` A STL patch for egcs 1.0.2 H.J. Lu
[not found] ` <m0y5H2p-00058KC.cygnus.egcs@ocean.lucon.org>
1998-02-19 10:45 ` (1.0.2) std/bastring.h change -- Why add std/bastring.cc? Jason Merrill
[not found] ` <m0y5H5T-00058KC.cygnus.egcs@ocean.lucon.org>
1998-02-19 10:47 ` A STL patch for egcs 1.0.2 Jason Merrill
1998-02-19 10:47 ` H.J. Lu [this message]
1998-02-19 12:42 ` Jason Merrill
1998-02-20 12:26 ` H.J. Lu
1998-02-20 12:26 ` Jason Merrill
1998-02-20 12:26 ` H.J. Lu
1998-02-20 11:09 ` Jason Merrill
1998-02-19 14:09 ` Ulrich Drepper
1998-02-22 16:39 ` Jeffrey A Law
1998-02-23 11:00 ` H.J. Lu
1998-02-23 9:19 ` Jeffrey A Law
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=m0y5azh-00058fC@ocean.lucon.org \
--to=hjl@lucon.org \
--cc=drepper@cygnus.com \
--cc=egcs@cygnus.com \
--cc=jason@cygnus.com \
/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).