Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 25 Feb 2004 09:45:23 -0800
From:      Marcel Moolenaar <marcel@xcllnt.net>
To:        Julian Elischer <julian@elischer.org>
Cc:        FreeBSD current users <current@freebsd.org>
Subject:   Re: TLS, Thread Local Storage..
Message-ID:  <20040225174522.GC58071@ns1.xcllnt.net>
In-Reply-To: <Pine.BSF.4.21.0402242349440.85856-100000@InterJet.elischer.org>
References:  <Pine.BSF.4.21.0402241557160.67378-100000@InterJet.elischer.org> <Pine.BSF.4.21.0402242349440.85856-100000@InterJet.elischer.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Feb 25, 2004 at 12:17:47AM -0800, Julian Elischer wrote:
> > 
> Who can tell me how well our linker understands what gcc puts out when
> given a __thread directive..

We need a binutils update anyway. The assembler doesn't understand
the output of the compiler on most platforms anyway. See also:
	http://people.freebsd.org/~marcel/tls.html

It says that only ia64 has full GNU toolchain support (which is
unsurprising).

> The BIG question is "who knows enough about the dynamic linker to be
> able to make this work for dynamic libraries..?" I gather that our
> dynamic linker is not the one that linux uses and is specific to us. (Am
> I wrong?)

No, you're correct. There's a big part for the dynamic linker to
make it all work.

The hard part for me now is how to distribute the related features
across kernel, rtld, libc and the various threading libraries to make
it work in all cases (ie complete vs shared, static vs dynamic and
threaded vs non-threaded) and without pessimizing non-TLS binaries.

-- 
 Marcel Moolenaar	  USPA: A-39004		 marcel@xcllnt.net



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040225174522.GC58071>