Ross Ridge wrote:
> Actually, the last one I haven't done yet. I've just been using a linker
> script to do that, but it should be in a library so the TLS directory
> entry isn't created if the executable doesn't use TLS.
Richard Henderson wrote:
> You can also create this in the linker, without
On Sun, Jun 04, 2006 at 07:05:55AM -0400, Ross Ridge wrote:
> FX Coudert wrote:
> > Now, for an idea of how much work it represents... perhaps someone
> >here can tell us?
>
> It's not too hard but it requires changing GCC and binutils, plus a
> bit of library support. In my implementation (more
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
FX Coudert wrote:
> Now, for an idea of how much work it represents... perhaps someone
>here can tell us?
It's not too hard but it requires changing GCC and binutils, plus a
bit of library support. In my implementation (more or less finished,
but I have had time to test it yet), I did the followi
