[M3devel] any limitations on __thread?

[jay.krell at cornell.edu]

It was to be done every time building m3core. Fast enough. I removed  
it for now. Pic makes it a smaller win, I have no numbers, and broke  
Tony's build. It would also reduce but not eliminate leak upon dynamic  
unload, which we should consider anyway.

It was in m3core/src/thread/pthread/m3makefile.

  - Jay (phone)

On Apr 30, 2009, at 2:18 AM, Olaf Wagner <wagner at elegosoft.com> wrote:

> Quoting Jay <jay.krell at cornell.edu>:
>
>>
>> Anyone have expertise on __thread?
>> In particular, on Windows there is a close analog  
>> __declspec(thread)  that generally would seem to work and work  
>> well, except that, per  documentation, prior to Vista, it doesn't  
>> work if you are loaded  with LoadLibrary (dlopen), only if the main  
>> executable uses your  .so, directly or indirectly. To me that's a  
>> pretty big limitation so  I wouldn't use it. I haven't seen any  
>> documentation on __thread  giving this caveat though so it seems ok  
>> to use.
>>
>> I changed m3core to use it if sample code seems to compile, link,   
>> and execute correctly with it.
>
> This is done at installation time, I assume?
> Where is this test located?
>
>>
>>
>> - Jay
>
>
>
> -- 
> Olaf Wagner -- elego Software Solutions GmbH
>               Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, Germ 
> any
> phone: +49 30 23 45 86 96  mobile: +49 177 2345 869  fax: +49 30 23 45 86 95
>   http://www.elegosoft.com | Geschäftsführer: Olaf Wagner | Sitz: Be 
> rlin
> Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr:  
> DE163214194
>
>