Date: Wed, 18 Jun 2003 16:29:18 -0700 From: Marcel Moolenaar <marcel@xcllnt.net> To: Julian Elischer <julian@elischer.org> Cc: threads@freebsd.org Subject: Re: Nvidia, TLS and __thread keyword -- an observation Message-ID: <20030618232918.GA65167@ns1.xcllnt.net> In-Reply-To: <Pine.BSF.4.21.0306181612230.41210-100000@InterJet.elischer.org> References: <20030618225517.GA64374@ns1.xcllnt.net> <Pine.BSF.4.21.0306181612230.41210-100000@InterJet.elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jun 18, 2003 at 04:13:16PM -0700, Julian Elischer wrote: > > > I deliberately don't want to deal with libc_r, but if people think > > we should make that work too than we simply don't deal with libc_r > > on ia64. > > unfortunatly we need to have binary compatibility between > lic_r and libkse/libthr for a while until they settle down. Ok. We'll treat ia64 as the exception then. We need to stop abusing setjmp()/longjmp() on ia64 ASAP. Whose going to look at i386 and other platforms? I mainly like to focus on ia64 while being supportive in all other cases (instead of being the driving force). -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030618232918.GA65167>