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: "triegel at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Wed, 24 Sep 2014 21:18:56 +0000
- Subject: [Bug nptl/16432] pthread_spin_unlock should imply a memory barrier
- Auto-submitted: auto-generated
- References: <bug-16432-131 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16432
--- Comment #7 from Torvald Riegel <triegel at redhat dot com> ---
I repeat: This bug is not a venue to discuss your (mis)understanding of the C11
memory model.
What you write is incorrect. Please read the standard again, or Batty et al's
formalization. Understand the difference between the sequenced-before and
synchronizes-with relations, and how they are combined and influence
happens-before.
--
You are receiving this mail because:
You are on the CC list for the bug.