From owner-freebsd-current@FreeBSD.ORG Sun Jun 27 10:02:54 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 42EEE16A4CE; Sun, 27 Jun 2004 10:02:54 +0000 (GMT) Received: from itchy.rabson.org (mailgate.nlsystems.com [80.177.232.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D0C043D2D; Sun, 27 Jun 2004 10:02:53 +0000 (GMT) (envelope-from dfr@nlsystems.com) Received: from ns0.nlsystems.com (ns0.nlsystems.com [80.177.232.243]) by itchy.rabson.org (8.12.11/8.12.11) with ESMTP id i5RA1vAN008311; Sun, 27 Jun 2004 11:01:57 +0100 (BST) (envelope-from dfr@nlsystems.com) From: Doug Rabson To: freebsd-current@freebsd.org Date: Sun, 27 Jun 2004 11:01:51 +0100 User-Agent: KMail/1.6.1 References: <20040626231720.GB11573@dragon.nuxi.com> <20040627041847.GA45235@dragon.nuxi.com> In-Reply-To: <20040627041847.GA45235@dragon.nuxi.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200406271101.51876.dfr@nlsystems.com> X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on itchy.rabson.org X-Virus-Scanned: clamd / ClamAV version 0.71, clamav-milter version 0.71 X-Virus-Status: Clean cc: Julian Elischer Subject: Re: Does -CURRENT's gcc generate ___tls_get_addr under any X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jun 2004 10:02:54 -0000 On Sunday 27 June 2004 05:18, David O'Brien wrote: > On Sat, Jun 26, 2004 at 04:39:33PM -0700, Julian Elischer wrote: > > On Sat, 26 Jun 2004, David O'Brien wrote: > > > On Fri, Jun 25, 2004 at 02:15:04PM -0700, Julian Elischer wrote: > > > > On Fri, 25 Jun 2004, Joe Marcus Clarke wrote: > > > > > On Fri, 2004-06-25 at 16:44, John Merryweather Cooper wrote: > > > > > > I'm working on porting (and getting fully working) > > > > > > lang/mono version 0.96, and I'm having a problem. In one > > > > > > of my object files--mini.lo--I'm getting an extern > > > > > > reference to ___tls_get_addr. I've been over the source > > > > > > code in mini.c > > > > > > ... > > > > > > > TLS is coming.. it's just not here yet.. > > > > > > By whom? I've done the part I committed to. Yet I've heard > > > nothing else about TLS in the two weeks after it was possible to > > > start work on the next part. > > > > Doug Rabson has partly working TLS in p4 and last I heard was > > awaiting some comments from the nvidia people who would be our > > first users of TLS. > > DFR has TLS particially working on i386-only (and in a way that > didn't need a Binutils upgrade to 2.15...). i386-only isn't > acceptable, and the deal with me if I went thru all the work to do a > binutils upgrade was that others would come along after that and make > TLS work on all FreeBSD platforms. Please, anyone who has time and hardware, look at (and fix) branches/kse in P4. I have typed in stubs for most architectures but the only non-i386 arch which is even close to compiling is ia64. The document http://people.redhat.com/drepper/tls.pdf is an invaluable source for the details of TLS on any particular architecture. There are simple test cases in tools/regression/tls. I believe that with the new binutils and existing compiler, support should be possible for i386, ia64 and amd64. The others probably need gcc 3.4.