Re: [Valgrind-users] helgrind and double checked initialization

[Jeffrey W. <nol...@gm...>]

Thanks Bart,

On Sun, Aug 28, 2011 at 12:26 PM, Bart Van Assche <bva...@ac...> wrote:
> On Sun, Aug 28, 2011 at 6:13 PM, Jeffrey Walton <nol...@gm...> wrote:
>> (1) Never trust wikipedia.
>
> Reading your message makes me wonder whether you are familiar with the
> reason why memory barriers exist,
I'm not aware that GCC will change the semantics of the program under
these conditions. I could be wrong, though.

> something the Wikipedia authors of
> the page about double-checked locking clearly are aware of ?
It does not change the fact that I do not trust wikipedia. I've found
too many mistakes of the years.

> the paper "x86-TSO: a rigorous and usable programmer's model for x86
> multiprocessors" might help. It does not only discuss memory models in
> general but also explains why effects like inter-processor store
> reordering are observed with certain processor families but not with
> x86 CPUs.
I've read a few papers (and try to follow relevant online
discussions), but I will fetch and read this one.

Thanks again,
Jeff