To answer the first part of your question, a locked xchg is the usual way to implement a sequentially consistent store on x86 without an explicit fence. For seq

To answer the first part of your question, a locked xchg is the usual way to implement a sequentially consistent store on x86 without an explicit fence. For sequentially consistent loads, plain mov suffices, providing it synchronizes with a locked store. http://stackoverflow.com/questions/4972106/sequentially-consistent-atomic-load-on-x86 http://stackoverflow.com/questions/4972106/sequentially-cons...