Subj : Re: Memory Barriers, Compiler Optimizations, etc.
To   : comp.programming.threads
From : Alexander Terekhov
Date : Sat Feb 05 2005 02:17 pm


Ziv Caspi wrote:
[...]
> Microsoft has already provided some guarantees here, as specified in
> http://www.microsoft.com/whdc/driver/kernel/MP_issues.mspx. In particular,
> it treats volatile reads as having acquire semantics, and volatile writes as
> having release semantics, so if you target CL 14 (or later), you have a
> solution. 

I doubt it. KeMemoryBarrier* idiocy and braindead illustrations from
that piece speak volumes to the contrary. 

regards,
alexander.

.