Subj : Re: Memory Barriers, Compiler Optimizations, etc.
To   : comp.programming.threads
From : Neill Clift [MSFT]
Date : Sun Feb 06 2005 10:37 pm

"SenderX" <xxx@xxx.com> wrote in message 
news:uOCdnVM_fvSaY5vfRVn-sQ@comcast.com...
>> So if you explain your issues in a way I can understand.
>> Clearly stating what you think is an issue I could send
>> details to the appropriate people and try and effect
>> change if I agree.
>
> Here are some questions that need clarification in your documentation:
>
> 1. Can external data depend on the return value from a failed CAS?

I don't undestand what your asking.

>
> 2. Does WaitFor_xxx_Object(s) API's have acquire semantics?

WaitForSingleObject etc as well as signallers like SetEvent have to
be full barriers. You can only signal a thread to do something if the
signal is a barrier to operations you did prior to the signal. The same
argument would apply to waits. Win32 programs would likely not
work without this and we wouldn't violate it.

.