From owner-freebsd-current@FreeBSD.ORG  Wed Mar 24 04:55:32 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 08CB316A580; Wed, 24 Mar 2004 04:55:31 -0800 (PST)
Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 3C2AE43D5C; Wed, 24 Mar 2004 04:55:30 -0800 (PST)
	(envelope-from eischen@vigrid.com)
Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4])
	by mail.pcnet.com (8.12.10/8.12.1) with ESMTP id i2OCtNtf023443;
	Wed, 24 Mar 2004 07:55:23 -0500 (EST)
Date: Wed, 24 Mar 2004 07:55:23 -0500 (EST)
From: Daniel Eischen <eischen@vigrid.com>
X-Sender: eischen@pcnet5.pcnet.com
To: Scott Long <scottl@freebsd.org>
In-Reply-To: <20040324002624.T55727@pooker.samsco.home>
Message-ID: <Pine.GSO.4.10.10403240754110.22672-100000@pcnet5.pcnet.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: Marcel Moolenaar <marcel@xcllnt.net>
cc: Julian Elischer <julian@elischer.org>
cc: FreeBSD current users <current@freebsd.org>
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
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Mar 2004 12:55:32 -0000

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.

-- 
Dan Eischen