Date: Wed, 24 Mar 2004 07:55:23 -0500 (EST) From: Daniel Eischen <eischen@vigrid.com> To: Scott Long <scottl@freebsd.org> Cc: FreeBSD current users <current@freebsd.org> Subject: Re: SF Bay area hackfest Message-ID: <Pine.GSO.4.10.10403240754110.22672-100000@pcnet5.pcnet.com> In-Reply-To: <20040324002624.T55727@pooker.samsco.home>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.10.10403240754110.22672-100000>