Date: Wed, 18 Jun 2003 19:17:28 -0400 From: Alexander Kabaev <ak03@gte.com> To: Marcel Moolenaar <marcel@xcllnt.net> Cc: threads@freebsd.org Subject: Re: Nvidia, TLS and __thread keyword -- an observation Message-ID: <20030618191728.2fc32bd9.ak03@gte.com> In-Reply-To: <20030618225517.GA64374@ns1.xcllnt.net> References: <20030618182638.GA63660@ns1.xcllnt.net> <Pine.BSF.4.21.0306181518520.39446-100000@InterJet.elischer.org> <20030618225517.GA64374@ns1.xcllnt.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 18 Jun 2003 15:55:17 -0700 Marcel Moolenaar <marcel@xcllnt.net> wrote: > On Wed, Jun 18, 2003 at 03:19:30PM -0700, Julian Elischer wrote: > > > > Marcel, are you (or do you kno of anyone else) doing anything on > > TLS? > > We can approach it like this (just an example to bootstrap the > work): > > o Agree on a version of GCC we'll use during prototyping or wait > for GCC to be updated in the tree. > o Implement static TLS in libthr. > o Test. > o Implement dynamic TLS in libthr and RTLD. Concurrently implement > static TLS in libkse. > o Test static TLS in libkse. > o Finish dynamic TLS in libthr/RTLD and start dynamic TLS in libkse. > o Test libthr (finish dynamic TLS in libkse). > o Test libkse. > > I deliberately don't want to deal with libc_r, but if people think > we should make that work too than we simply don't deal with libc_r > on ia64. I announced my intention to work on rtld side of TLS support some time ago and I already have some work in progress. Interested parties can easily compile GCC 3.3 port with TLS support. Run 'make patch' in the ports directory and then edit work/gcc-3.3/gcc/configure to look for binutils 2.13 instead of 2.14 while testing for the platform TLS support. Compile and install the port. -- Alexander Kabaev
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030618191728.2fc32bd9.ak03>