Re: [Mingw-w64-public] problem with TLS and DLL

2013-12-22 Thread Daniel Villeneuve
On 22/12/13 12:00 PM, Kai Tietz wrote: > 2013/12/22 Daniel Villeneuve : >> Is the dynamic library vs extern thread-local limitation you bring >> above specific to Mingw-w64's implementation? or applicable to >> Windows in general? > It applies to thread-local variables in general. Especially for >

Re: [Mingw-w64-public] problem with TLS and DLL

2013-12-22 Thread Kai Tietz
2013/12/22 Daniel Villeneuve : > Hello Kai, > > On 22/12/13 05:13 AM, Kai Tietz wrote: >> Hello Daniel, >> >> 2013/12/21 Daniel Villeneuve : >>> Hi, >>> >>> I have a DLL library which declares an "extern __thread int iTlsExtern" >>> variable, which I can access from the library and from a program.

Re: [Mingw-w64-public] problem with TLS and DLL

2013-12-22 Thread Daniel Villeneuve
Hello Kai, On 22/12/13 05:13 AM, Kai Tietz wrote: > Hello Daniel, > > 2013/12/21 Daniel Villeneuve : >> Hi, >> >> I have a DLL library which declares an "extern __thread int iTlsExtern" >> variable, which I can access from the library and from a program. >> >> However, modifications made from the

Re: [Mingw-w64-public] problem with TLS and DLL

2013-12-22 Thread Kai Tietz
Hello Daniel, 2013/12/21 Daniel Villeneuve : > Hi, > > I have a DLL library which declares an "extern __thread int iTlsExtern" > variable, which I can access from the library and from a program. > > However, modifications made from the library to iTlsExtern are not > seen from the program. > > Thi

[Mingw-w64-public] problem with TLS and DLL

2013-12-22 Thread Daniel Villeneuve
Hi, I have a DLL library which declares an "extern __thread int iTlsExtern" variable, which I can access from the library and from a program. However, modifications made from the library to iTlsExtern are not seen from the program. This seems to come from the fact that the address of the variabl