[Bug testsuite/51038] [4.7 Regression]: 29_atomics/atomic_flag/clear/1.cc test_and_set/explicit.cc implicit.cc

amacleod at redhat dot com gcc-bugzilla@gcc.gnu.org
Thu Nov 10 17:05:00 GMT 2011


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51038

Andrew Macleod <amacleod at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2011-11-10
     Ever Confirmed|0                           |1

--- Comment #1 from Andrew Macleod <amacleod at redhat dot com> 2011-11-10 16:21:44 UTC ---
The issue here is no atomic support whatsoever.  The standard now *requires*
that atomic_flag be implementable in a lock free manner for compliance.

In order to support atomic_flag in a lock free manner on a target, we need at a
minimum the legacy __sync_lock_test_and_set and __sync_lock_release to be
implemented.

Previous to this release, if atomic_flag couldn't be implemented lock free, it
was implemented with locks.  libstdc++-v3 no longer supports any locked
implementations.



More information about the Gcc-bugs mailing list