[cpp-threads] modes, pass 2

[Peter Dimov]

Alexander Terekhov wrote:
> On 5/8/05, Doug Lea <dl at cs.oswego.edu> wrote:
> [...]
>> The "ordered" suffix needs a better name, but the intent
>> is that it is the lightest barrier (often no-op) that
>> prevents re-orderings of successive loads (for get_ordered)
>> or stores (for set_ordered) or operations on the same
>> variable (for CAS_ordered).
>
> I think it's implied on all existing hardware. E.g. see Load Hit
> Store/Store Hit Load/Load Hit Load stuff here:

Isn't this just basic uniprocessor consistency? I thought that "ordered" had 
a more sinister meaning. :-)