Date: Wed, 25 Feb 2004 10:09:22 -0800 From: Marcel Moolenaar <marcel@xcllnt.net> To: Alexander Kabaev <ak03@gte.com> Cc: FreeBSD current users <current@freebsd.org> Subject: Re: TLS, Thread Local Storage.. Message-ID: <20040225180922.GB58265@ns1.xcllnt.net> In-Reply-To: <20040225130455.672f28f6@kanpc.gte.com> References: <Pine.BSF.4.21.0402241557160.67378-100000@InterJet.elischer.org> <Pine.BSF.4.21.0402242349440.85856-100000@InterJet.elischer.org> <20040225174522.GC58071@ns1.xcllnt.net> <20040225130455.672f28f6@kanpc.gte.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Feb 25, 2004 at 01:04:55PM -0500, Alexander Kabaev wrote: > On Wed, 25 Feb 2004 09:45:23 -0800 > Marcel Moolenaar <marcel@xcllnt.net> wrote: > > > 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 > > > There was a missed merge from stock GCC 3.3 code that I failed to add to > local config files in FreeBSD CVS and that resulted in GCC spewing > assembly output which as could't understand. This bug was fixed some > time ago. Ok. I assume this applies to i386 and amd64 only and that alpha and sparc64 still lack compiler support for it or are alpha and sparc64 fixed too? -- 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?20040225180922.GB58265>