[fpc-devel] volatile variables

Andrew Brunner andrew.t.brunner at gmail.com
Tue Jun 28 15:05:58 CEST 2011


On Tue, Jun 28, 2011 at 8:00 AM, Jonas Maebe <jonas.maebe at elis.ugent.be> wrote:
>
> On 28 Jun 2011, at 14:58, Andrew Brunner wrote:
>
>> On Tue, Jun 28, 2011 at 6:14 AM, Michael Schnell <mschnell at lumino.de>
>> wrote:
>>
>>> For variables not defined as volatile, (e.g.) pthread_mutex (and similar
>>> stuff on Windows) can be used to protect them.
>>>
>> A mutex may be able to atomically block access because of its own
>> memory barrier, but I would suggest that employing such a technique on
>> multi-core systems will not ensure an accurate value.
>
> pthread_mutex() does guarantee that. I don't know about the Windows
> equivalents.
>

Specification just describes standard mutex.  What makes pthreads
specification different to include ordering?



More information about the fpc-devel mailing list