Subj : Re: Memory visibility and MS Interlocked instructions
To   : comp.programming.threads
From : Alexander Terekhov
Date : Sat Aug 27 2005 10:48 pm


Joe Seigh wrote:
[...]
> just trying to save Intel from themselves.  It's not a
> correctness of implementation issue, it's a performance

Under x86 memory model, all loads (including dependent ones) behave 
in-order with respect to preceding loads. Processor can perform out-
of-order speculative loads but they never yield incorrect results 
(processor detects memory ordering violations and rolls back). 

regards,
alexander.

.