Date: Thu, 22 Mar 2007 11:24:52 -0700 From: "Kip Macy" <kip.macy@gmail.com> To: "Daniel Eischen" <deischen@freebsd.org> Cc: Jason Evans <jasone@frebsd.org>, freebsd-threads@freebsd.org Subject: Re: lipthread and TLS Message-ID: <b1fa29170703221124l5a3be08fo6fa036866200e02c@mail.gmail.com> In-Reply-To: <Pine.GSO.4.64.0703221410310.9927@sea.ntplx.net> References: <2779e6080703220210u321522c7l40cf8555cfdc2404@mail.gmail.com> <4602B28C.1020204@elischer.org> <Pine.GSO.4.64.0703221312150.9927@sea.ntplx.net> <4602C49D.3080109@frebsd.org> <Pine.GSO.4.64.0703221410310.9927@sea.ntplx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 3/22/07, Daniel Eischen <deischen@freebsd.org> wrote: > On Thu, 22 Mar 2007, Jason Evans wrote: > > > Daniel Eischen wrote: > >> The toolchain itself should support TLS, so that's probably > >> the place to look, as well as src/libexec/rtld-elf/. The > >> libpthread library does not use TLS itself, and I don't > >> think anything (yet) uses TLS in libc or in our base system, > >> though I could be wrong. > > > > malloc uses TLS. > > Well, I stand corrected then. If you need to get MIPS up > and running without TLS, you may need to hack malloc() > and anything else that uses TLS to temporarily use > pthread_[gs]etspecific()... You won't be able to use TLS unless: a) initialization works in libc - it was broken on sparc64 until recently for both static and dynamic linking b) your linker supports it - the current binutils is very much out of date, users needing it will have to build a private toolchain
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b1fa29170703221124l5a3be08fo6fa036866200e02c>