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: <jason_merrill at redhat dot com>
- Subject: Re: libstdc was not safe in 2.92, is it now in 3.X?
- From: "Andrew B. Lundgren" <Andrew dot Lundgren at Level3 dot com>
- Date: Thu, 30 Aug 2001 09:15:14 -0600 (MDT)
- cc: <libstdc++ at gcc dot gnu dot org>
Thank you for the confirmation. May it not come up again until the next release! :)
On 30 Aug 2001 jason_merrill@redhat.com wrote:
> >>>>> "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
>
--
Andrew Lundgren
Andrew.Lundgren@level3.com