This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/54006] __atomic_always_lock_free inconsistent with __GCC_ATOMIC_INT_LOCK_FREE et al.
- 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: Fri, 20 Jul 2012 04:16:20 +0000
- Subject: [Bug c/54006] __atomic_always_lock_free inconsistent with __GCC_ATOMIC_INT_LOCK_FREE et al.
- Auto-submitted: auto-generated
- References: <bug-54006-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54006
--- Comment #3 from Hans-Peter Nilsson <hp at gcc dot gnu.org> 2012-07-20 04:16:20 UTC ---
Created attachment 27842
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=27842
Patch using can_compare_and_swap_p but with multiple problems
Besides the SEGV due to the initialization problem aleady mentioned, this patch
codifies the assumption that atomic intrinsic library functions (i.e.
libgcc-style) aren't lock-free, which is wrong but at least consistent with the
conceptual patch in PR54003.