Re: configure's __thread test

if i recall correctly, we ended up not using thread local variables 
because they weren't available in gcc at the time, but stubbed them out 
for the future.  we could revisit them and perhaps get a faster 
implementation by using them for the language registers.  i'm not 
convinced it would improve over the current strategy though.

in the meanwhile, i should disable the configure scripts tests for 
thread local variables...

jonathan

On Nov 22, 2003, at 6:56 PM, Faried Nawaz wrote:

> __thread isn't used in any .c files, but the configure script tests for
> it.  gcc's docs say
>
>     The `__thread' specifier may be applied to any global, file-scoped
>     static, function-scoped static, or static data member of a class.  
> It
>     may not be applied to block-scoped automatic or non-static data 
> member.
>
> The code that the configure script tries to compile is
>
> #include "confdefs.h"
>
> int main() {
> __thread int testvar;
> ; return 0; }
>
> which, given the above, fails to compile with any recent gcc.
>
>
> Faried.
> -- 
> The Great GNU has arrived, infidels, behold his wrath !
> "If a MOO runs on a port no one accesses, does it run?"
>
>