Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 07 Jun 2004 14:30:55 +0100
From:      Doug Rabson <dfr@nlsystems.com>
To:        Daniel Eischen <eischen@vigrid.com>
Cc:        freebsd-current@freebsd.org
Subject:   Re: HEADS UP! KSE needs more attention
Message-ID:  <1086615054.10911.17.camel@builder02.qubesoft.com>
In-Reply-To: <Pine.GSO.4.10.10406070912400.6934-100000@pcnet5.pcnet.com>
References:  <Pine.GSO.4.10.10406070912400.6934-100000@pcnet5.pcnet.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 2004-06-07 at 14:14, Daniel Eischen wrote:
> On Mon, 7 Jun 2004, Doug Rabson wrote:
> 
> > On Sunday 06 June 2004 20:55, Daniel Eischen wrote:
> > > On Sun, 6 Jun 2004, Scott Long wrote:
> > > > All,
> > > >
> > > > We are about 4-6 weeks away from starting the 5.3 release cycle. 
> > > > As it stands, KSE still only works reliably on i386.  There are
> > > > reports of significant instability on amd64, and it doesn't work at
> > > > all on alpha and sparc64.  I'm willing to drop the alpha
> > > > requirement and maybe even the sparc64 requirement, but there
> > > > absolutely will not be a 5.3 until amd64 is solid.  Please contact
> > > > myself, Dan Eischen, and David Xu if you are interested in helping
> > > > out.
> > >
> > > amd64 looks to be a problem in readline which doesn't seem
> > > to redispatch signal handlers with SA_SIGINFO arguments.
> > >
> > > David also has patches for debugging support at:
> > >
> > >   http://people.freebsd.org/~davidxu/kse/dbg/
> > >
> > > Doug Rabson also has basic TLS support working in perforce.
> > > It'd be nice to get TLS and debugging in before 5.3-release.
> > 
> > I'll probably try to commit some kind of TLS support into current in the 
> > next couple of weeks. Its likely to only support i386 and will be 
> > stubbed out for other platforms. Right now, I'm just waiting for some 
> > kind of feedback from an nvidia developer whos testing it.
> 
> Are you using the extra (*(%gs)->tls) to get TLS?

Yes. Our compiler always generates code like this:

	movl	%gs:0,%eax
	movl	1234,%ntpoff(foo)(%eax)





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1086615054.10911.17.camel>