This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: libstdc++/5037: Multithreaded read access to strings not threadsafe on Solaris/Sparc
- From: Craig <ckaes at jabber dot com>
- To: ljrittle at gcc dot gnu dot org
- Cc: gcc-bugs at gcc dot gnu dot org, gcc-gnats at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org
- Date: Thu, 06 Dec 2001 14:54:16 -0700
- Subject: Re: libstdc++/5037: Multithreaded read access to strings not threadsafe on Solaris/Sparc
- References: <20011206210847.27359.qmail@sources.redhat.com>
[craigk:/opt/tools/gcc-3.0/include/g++-v3/sparc-sun-solaris2.7/bits]$
head -1 atomicity.h
// Low-level functions for atomic operations: Sparc32 version -*- C++
-*-
For giggles, I tried running the test program w/ 3.0.2 about an hour
ago. It fails.
--C
ljrittle@gcc.gnu.org wrote:
>
> Synopsis: Multithreaded read access to strings not threadsafe on Solaris/Sparc
>
> State-Changed-From-To: open->feedback
> State-Changed-By: ljrittle
> State-Changed-When: Thu Dec 6 13:08:46 2001
> State-Changed-Why:
> OK, I looked at build.log and I do see that gcc is reporting
> a reasonable thread model. Can you verify that
> config/cpu/sparc/sparc32/bits/atomicity.h is being used
> to implement the spinlocks used by string<>? This file
> was installed on your system in
> $prefix/include/g++-v3/<target-triple>/bits/atomicity.h .
> First of all, make sure the one installed is not the
> generic copy of atomicity.h (internally labelled:
> Generic version). Thanks for your help.
>
> http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=5037&database=gcc