Double Checked Locking

[Sean Kelly]

On Dec 19, 2011, at 7:18 AM, Manfred_Nowak wrote:

> Regan Heath wrote:
>> after reading Andrei's link I'm not so sure..
> 
> If Andrei's conclusions are correct, then they are correct even for
> - the compilers under which an OS is compiled and
> - the hardware on which the OS runs.
> 
> I.e. if there is a "you loose" for the application programmer then there is  
> a "you loose" for the OS programmer and the engineer of the hardware too.
> 
> Does anyone except Andrei see what this means?

Not sure I understand the question, but if you look at the source of the Linux kernel, for example, it uses explicit memory barriers and other tricks to ensure a correct result.