Date: Wed, 18 Jun 2003 15:55:17 -0700 From: Marcel Moolenaar <marcel@xcllnt.net> To: Julian Elischer <julian@elischer.org> Cc: threads@freebsd.org Subject: Re: Nvidia, TLS and __thread keyword -- an observation Message-ID: <20030618225517.GA64374@ns1.xcllnt.net> In-Reply-To: <Pine.BSF.4.21.0306181518520.39446-100000@InterJet.elischer.org> References: <20030618182638.GA63660@ns1.xcllnt.net> <Pine.BSF.4.21.0306181518520.39446-100000@InterJet.elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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? Not in the context of FreeBSD. I used to be involved 2 years ago (roughly) in my daytime job and have experience from a tool-chain point of view and have been close to the fire WRT RTLD and pthread work. If we think this is important to have for 5.2, I can make time to work on it. I do ask for a good planning in that case, because there's a lot of work on my plate that I cannot yet delegate to others (read: ia64 work)... 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. -- 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?20030618225517.GA64374>