From owner-freebsd-current@FreeBSD.ORG Wed Mar 24 10:22:05 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 F2ABF16A4CE for ; Wed, 24 Mar 2004 10:22:04 -0800 (PST) Received: from smtp.mho.com (smtp.mho.net [64.58.4.5]) by mx1.FreeBSD.org (Postfix) with SMTP id C876643D1D for ; Wed, 24 Mar 2004 10:22:04 -0800 (PST) (envelope-from scottl@freebsd.org) Received: (qmail 24350 invoked by uid 1002); 24 Mar 2004 18:22:02 -0000 Received: from unknown (HELO freebsd.org) (64.58.1.252) by smtp.mho.net with SMTP; 24 Mar 2004 18:22:02 -0000 Message-ID: <4061D0ED.1040100@freebsd.org> Date: Wed, 24 Mar 2004 11:18:21 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040304 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daniel Eischen , "David O'Brien" References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: Marcel Moolenaar cc: Julian Elischer cc: FreeBSD current users 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 18:22:05 -0000 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 ??? 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