This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/70191] libatomic library does not have lock-free implementation for 16-bytes data object on Solaris
- From: "alexey.lapshin at oracle dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 11 Mar 2016 16:21:17 +0000
- Subject: [Bug c/70191] libatomic library does not have lock-free implementation for 16-bytes data object on Solaris
- Auto-submitted: auto-generated
- References: <bug-70191-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70191
Alexey Lapshin <alexey.lapshin at oracle dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|INVALID |FIXED
--- Comment #2 from Alexey Lapshin <alexey.lapshin at oracle dot com> ---
Correct. But it seems that libatomic library does not check existence of
cmpxchg16b. Thus it would use locked implementation even if target supports
cmpxchg16b.
i.e. old compiled code should work correctly with newly compiled code. If old
code has call to __atomic_load_16 and new code has inlined implementation -
they would work incorrectly.