Subj : Re: Consistency of a byte shared variable
To   : comp.programming.threads
From : SenderX
Date : Tue Feb 01 2005 01:32 am

> Could the example "ever" abort in B3 under the POSIX memory visibility 
> rules?

I currently assume POSIX lays out a memory model based on stringent 
acquire/release semantics:


sem_post( ... ) == release barrier "before" sema inc is made visible


sem_wait( ... ) == acquire barrier "after" sema dec is made visible


Does POSIX standard "explicitly" guarantee this type of straight forward 
memory model? If so, where is it documented?

.