This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/54005] New: Use __atomic_always_lock_free in libstdc++ is_lock_free instead of __atomic_is_lock_free
- From: "hp at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 17 Jul 2012 21:39:07 +0000
- Subject: [Bug libstdc++/54005] New: Use __atomic_always_lock_free in libstdc++ is_lock_free instead of __atomic_is_lock_free
- Auto-submitted: auto-generated
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54005
Bug #: 54005
Summary: Use __atomic_always_lock_free in libstdc++
is_lock_free instead of __atomic_is_lock_free
Classification: Unclassified
Product: gcc
Version: 4.8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: hp@gcc.gnu.org
CC: amacleod@redhat.com
Depends on: 54004
According to http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2009/n2992.htm,
the is_lock_free property goes for all instances of a given type. So,
libstdc++ should use __atomic_always_lock_free instead of __atomic_is_lock_free
as it does now, at r189499, libstdc++-v3/include/bits/atomic_base.h. But
first, better fix the depended bugs.