This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: libstdc++/3584: arm-specific atomic operations not atomic
- From: rearnsha at gcc dot gnu dot org
- To: acnrf at dial dot eunet dot ch, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org, rearnsha at arm dot com, robin dot farine at terminus dot org
- Date: 3 Oct 2002 16:17:27 -0000
- Subject: Re: libstdc++/3584: arm-specific atomic operations not atomic
- Reply-to: rearnsha at gcc dot gnu dot org, acnrf at dial dot eunet dot ch, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org, rearnsha at arm dot com, robin dot farine at terminus dot org, gcc-gnats at gcc dot gnu dot org
Synopsis: arm-specific atomic operations not atomic
State-Changed-From-To: feedback->closed
State-Changed-By: rearnsha
State-Changed-When: Thu Oct 3 09:17:26 2002
State-Changed-Why:
I'm closing this because there doesn't seem to be much more that can be done other than reverting back to the generic (no thread safety) model, which is what I've just done.
See http://gcc.gnu.org/ml/gcc-patches/2002-10/msg00157.html
for further details on the problem with the old code.
If thread support is added to the generic model, then we can make use of that on ARM too.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=3584