Subj : Re: Can C++ local static objects be made thread safe?
To   : comp.programming.threads
From : Alexander Terekhov
Date : Wed Feb 16 2005 06:29 pm


Gianni Mariani wrote: 

[... struggling SGI ...]

Quoting SGI's docu:

----
For programs under the IRIX 5.3 and above, segments with the
PF_MIPS_LOCAL flag set will be thread-local and not shared in 
the event of an sproc(2) system call. 

[...]

The sproc model of threading is incompatible with POSIX threads.
Attempts to create an sproc process from a pthreaded program will 
be rejected [see pthreads(5)].
----

Contrast it with {less struggling} Intel's* docu (C/C++ ABI):

----
Address-of operator

The address-of operator, &, can be applied to a thread-local 
variable. This operator is evaluated at runtime, and returns 
the address of the variable within the current thread. The 
address obtained by this operator may be used freely by any 
thread in the process as long as the thread that evaluated 
the address remains in existence. When a thread terminates, 
any pointers to thread-local variables in that thread become 
invalid.
----

And, BTW, see also

http://www.redhat.com/docs/manuals/enterprise/RHEL-3-Manual/gcc/thread-local.html
(When the address-of operator is applied to a thread-local...)

regards,
alexander.

*) Identical snippet from SUN's sun_docs/C/solaris_9/SUNWdev/LLM/p58.html
aside for a moment. ;-)

.