Subj : Re: pthread_getspecific or __thread for signal handler?
To   : comp.programming.threads
From : Loic Domaigne
Date : Wed Feb 02 2005 11:36 pm


>>Async safety isn't an issue if you don't use async unsafe functions
>>in your signal handler.  
> 
> 
> __thread stuff is nothing but syntactic sugar for pthread_[get/set]
> specific(). And all pthread calls are async-signal-unsafe.

No, not necessarily async-signal-unsafe. Rather "not forced to be 
async-signal-safe", which doesn't mean that they necessarily aren't.

I wouldn't be surprise if __thread stuff on Linux is async-signal-safe 
(and remember, portability wasn't the concern of the poster).

Loic.

.