This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: libstdc was not safe in 2.92, is it now in 3.X?
- To: "Andrew B. Lundgren" <Andrew dot Lundgren at Level3 dot com>
- Subject: Re: libstdc was not safe in 2.92, is it now in 3.X?
- From: Jason Merrill <jason_merrill at redhat dot com>
- Date: 30 Aug 2001 16:06:54 +0100
- Cc: <libstdc++ at gcc dot gnu dot org>
- References: <Pine.GSO.4.33.0108281627300.5805-100000@anaconda.vdev.level3.net>
>>>>> "Andrew" == Andrew B Lundgren <Andrew.Lundgren@Level3.com> writes:
> So it is now thread safe according to the SGI definition where as it was
> not before correct?
Yes.
> At what version did it become thread safe according to the SGI definition?
Most of the library code came from the SGI STL implementation; the problem
with thread-safety was the reference-counting string implementation.
Locking primitives were added to the string class for sparc and x86 in the
2.95 releases; the string class became thread-safe on other platforms only
in 3.0.
Jason