Subj : Re: Non-strictly-conforming and unspecified versus undefined behavior
To   : comp.programming.threads,comp.std.c
From : Alexander Terekhov
Date : Tue Feb 22 2005 10:48 am


Gianni Mariani wrote:
[...]
> If you require threads to be able to share thread specific objects,
> they're, by defintion, no longer thread specific !  Kind of an oxymoron.

__thread lvalues designate different objects depending on thread. The
mappings are "thread specific", but objects are not (apart from having
"thread-specific" lifetimes). They are not "thread-private". Just like
objects with automatic storage duration are not "thread-private". Got
it?

regards,
alexander.

.