From owner-freebsd-arch Sat May 12 5: 6:30 2001 Delivered-To: freebsd-arch@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 94A7937B423 for ; Sat, 12 May 2001 05:06:27 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id IAA15937; Sat, 12 May 2001 08:05:38 -0400 (EDT) Date: Sat, 12 May 2001 08:05:38 -0400 (EDT) From: Daniel Eischen To: Bruce Evans Cc: arch@FreeBSD.org Subject: Re: cvs commit: src/sys/i386/linux linux_sysvec.c In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ Moved to -arch ] On Sat, 12 May 2001, Bruce Evans wrote: > On Fri, 11 May 2001, Daniel Eischen wrote: > > > deischen 2001/05/11 20:23:14 PDT > > > > Modified files: > > sys/i386/linux linux_sysvec.c > > Log: > > Preserve the state of the %gs register when setting up the signal > > handler in Linux emulation. According to bde, this is what Linux > > does. > > > > Recent versions of linuxthreads use %gs for thread-specific data, > > while FreeBSD uses %fs (mostly because WINE uses %gs). > > I think FreeBSD should use %gs too (except I think segment registers > should never be used). Are there different compatibility problems > with WINE? Using %gs is OK by me. I've never used WINE, so I'm not sure how it uses %gs. I think Terry raised the issue when we were discussing which register to use on -arch, and at the time nobody seemed to care if we used %fs or %gs. I suppose using %gs would conflict with WINE if it ever relied on our native threads libraries. But since Linux uses %gs, and WINE is more likely to run under Linux than anything else, it would seem safe for FreeBSD to use %gs also. -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message