Subj : Re: Can C++ local static objects be made thread safe?
To   : comp.programming.threads
From : David Schwartz
Date : Thu Feb 24 2005 12:30 pm


"Giancarlo Niccolai" <noone@nothing.it> wrote in message 
news:cvklr4$sgl$1@fata.cs.interbusiness.it...

> I just protested for this thing.
>
> I also wrote to ABI C++.

    There's nothing wrong with the C++ ABI. As I understand it, it leaves 
space for a flag to indicate whether an object has been initialized or not. 
It doesn't *require* locks during initialization. If it did, the G++ option 
to avoid them would violate the standard.

    The examples the ABI uses to justify the change are *not* pthreads 
examples.

> We must call in the PTHREAD committee. Is any of them reading?

    Why? The pthreads standard is absolutely clear and not in error. The C++ 
ABI is absolute clear and not in error. The problem is strictly in G++, 
which doesn't turn the locking off when the programmer specifically 
indicates that he has locked all cases where data may be shared (implied by 
'-pthreads').

    DS

.