From owner-freebsd-current@FreeBSD.ORG Wed Mar 24 11:44:23 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 558FB16A4CE; Wed, 24 Mar 2004 11:44:23 -0800 (PST) Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [216.148.227.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4473743D1D; Wed, 24 Mar 2004 11:44:23 -0800 (PST) (envelope-from julian@elischer.org) Received: from interjet.elischer.org ([24.7.73.28]) by comcast.net (rwcrmhc12) with ESMTP id <2004032419442201400stigre>; Wed, 24 Mar 2004 19:44:22 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id LAA63957; Wed, 24 Mar 2004 11:47:39 -0800 (PST) Date: Wed, 24 Mar 2004 11:47:38 -0800 (PST) From: Julian Elischer To: Scott Long In-Reply-To: <4061D0ED.1040100@freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Marcel Moolenaar cc: FreeBSD current users cc: David O'Brien Subject: Re: SF Bay area hackfest 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: Wed, 24 Mar 2004 19:44:23 -0000 On Wed, 24 Mar 2004, Scott Long wrote: > Daniel Eischen wrote: > > On Wed, 24 Mar 2004, Scott Long wrote: > > > > > >>On Wed, 24 Mar 2004, Daniel Eischen wrote: > >> > >>>>What happens when the compiler, toolchain, etc, etc, are all updated to > >>>>make TLS work, but the user libmaps C_R in? Does stuff blow up? I'm ok > >>>>with C_R not explicitely supporting it so long as it doesn't create new > >>>>failure cases. > >>> > >>>I guess stuff blows up, probably very similar to what already > >>>happens when someone tries to use nvidia drivers/openGL with > >>>libpthread or libthr. But as far as I know, nothing we have > >>>is currently built to use it (it probably can't be because > >>>our released toolchain first needs to support it). > >>> > >> > >>This isn't terribly desirable since C_R is going to be the fallback thread > >>package for 5.x. Is there any way for C_R to detect when it's in a > >>position to blow up and/or give an intelligent message to the user? > > > > > > It's probably easier just to add TLS support to libc_r if it's > > highly desirable. > > > > Note that it's highly desirable, but not the highest priority. > > So our table is now: > > > Task Owner > > Import new GCC Alexander Kabaev > Import new binutils ??? > Modify loader (image activator?) > to understand TLS ??? > Modify KSE to understand TLS Dan Eischen/David Xu > Modify dynamic linker for TLS Doug Rabson > Modify THR to understand TLS ??? > Modify C_R to understand TLS ??? dogsbody and 2nd set of eyes.. julian(will be working with everyone I think) > > It looks like we are gaining critical mass on this. C_R and THR are > less important, and I'd even be willing to take a look at them myself. > David, can you help with the binutils? It sounds like there might be > some issues with libbfd if binutils is upgraded but gdb is not. Can we > discuss the options here? > > Thanks, > > Scott >