libstdc++/5037: Multithreaded read access to strings not threadsafe on Solaris/Sparc

Craig ckaes@jabber.com
Thu Dec 6 13:56:00 GMT 2001


The following reply was made to PR libstdc++/5037; it has been noted by GNATS.

From: Craig <ckaes@jabber.com>
To: ljrittle@gcc.gnu.org
Cc: gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org,
 	gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org
Subject: Re: libstdc++/5037: Multithreaded read access to strings not threadsafe 
 on Solaris/Sparc
Date: Thu, 06 Dec 2001 14:54:16 -0700

 [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



More information about the Gcc-prs mailing list