On Sun, Jun 04, 2006 at 02:03:05PM +0200, Piotr Wyderski wrote:
> fs:[0x14] is a per-thread 32-bit word available for applications,
> so you can store a pointer to your own TLS array there.
I don't think we can hijack this.
> fs:[0x2c] points to a Windows-specific TLS array, so you can
> make us
Hi, all,
After I refer to the Intel paper titled "Threading
Methodology : Principles and Practices" versin 2.0
published in 2003, I note the following message in the
article mentioning:(from page 22, web site :
http://cache-www.intel.com/cd/00/00/21/93/219349_threadingmethodology.pdf)
___
FX Coudert wrote:
The support for TLS (Thread Local Storage) would probably come from
the compiler itself. Windows has TLS (see for example http://
dotnet.di.unipi.it/Content/sscli/docs/doxygen/pal/localstorage_8c-
source.html and http://www.ddj.com/dept/cpp/184403874, or the MSDN
documenta
[First, a warning: I'm neither an expert in TLS, nor in Windows nor
in GCC guts
can we have chance to solve the
problem of threadprivate by adding the TLS support to
mingw32?
The support for TLS (Thread Local Storage) would probably come from
the compiler itself. Windows has TLS (see for e
