From owner-freebsd-threads@FreeBSD.ORG Wed Jun 18 15:55:52 2003 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0349837B401 for ; Wed, 18 Jun 2003 15:55:52 -0700 (PDT) Received: from ns1.xcllnt.net (209-128-86-226.bayarea.net [209.128.86.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 33CB943FB1 for ; Wed, 18 Jun 2003 15:55:51 -0700 (PDT) (envelope-from marcel@xcllnt.net) Received: from ns1.xcllnt.net (localhost [127.0.0.1]) by ns1.xcllnt.net (8.12.9/8.12.9) with ESMTP id h5IMtHDZ065137; Wed, 18 Jun 2003 15:55:17 -0700 (PDT) (envelope-from marcel@ns1.xcllnt.net) Received: (from marcel@localhost) by ns1.xcllnt.net (8.12.9/8.12.9/Submit) id h5IMtHn7065136; Wed, 18 Jun 2003 15:55:17 -0700 (PDT) Date: Wed, 18 Jun 2003 15:55:17 -0700 From: Marcel Moolenaar To: Julian Elischer Message-ID: <20030618225517.GA64374@ns1.xcllnt.net> References: <20030618182638.GA63660@ns1.xcllnt.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.1i cc: David Xu cc: threads@freebsd.org Subject: Re: Nvidia, TLS and __thread keyword -- an observation X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Jun 2003 22:55:52 -0000 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