This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: libstdc++/5347: implementation is not thread-safe on multi-processor machines
- From: ljrittle at gcc dot gnu dot org
- To: gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, ljrittle at gcc dot gnu dot org, markus dot breuer at materna dot de, nobody at gcc dot gnu dot org
- Date: 16 Jan 2002 01:36:08 -0000
- Subject: Re: libstdc++/5347: implementation is not thread-safe on multi-processor machines
- Reply-to: ljrittle at gcc dot gnu dot org, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, ljrittle at gcc dot gnu dot org, markus dot breuer at materna dot de, nobody at gcc dot gnu dot org, gcc-gnats at gcc dot gnu dot org
Synopsis: implementation is not thread-safe on multi-processor machines
Responsible-Changed-From-To: unassigned->ljrittle
Responsible-Changed-By: ljrittle
Responsible-Changed-When: Tue Jan 15 17:36:08 2002
Responsible-Changed-Why:
Mine.
State-Changed-From-To: open->closed
State-Changed-By: ljrittle
State-Changed-When: Tue Jan 15 17:36:08 2002
State-Changed-Why:
Duplicate of libstdc++/5037 (which is closed since it is
fixed on mainline for 3.1 and, if ever released, 3.0.4+).
I have tested this case against a patched copy of gcc
3.0.3 on an MP sparc and it works without crashing.
I have attached the patch against gcc-3.0.3.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5347