> Are there any objections to the following compare-and-swap? > Basically, it adds another parameter specifying the memory > synchronization for the load-only-write-did-not-happen case. Are there reasonable ways on existing implementations to implement the full flexibility of this? It seems pretty inventive to me. Clark