This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug nptl/16432] pthread_spin_unlock should imply a memory barrier
- From: "fweimer at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Wed, 10 Apr 2019 11:52:11 +0000
- Subject: [Bug nptl/16432] pthread_spin_unlock should imply a memory barrier
- Auto-submitted: auto-generated
- References: <bug-16432-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16432
Florian Weimer <fweimer at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |fweimer at redhat dot com
Resolution|--- |INVALID
Flags| |security-
--- Comment #8 from Florian Weimer <fweimer at redhat dot com> ---
I agree with Torvald: I believe the x86 implementation is correct as-is.
If you want a portable memory barrier, you can use <stdatomic.h>, C++ <atomic>,
or the GCC __atomic builtins (depending on your exact portability needs).
--
You are receiving this mail because:
You are on the CC list for the bug.