Date: Fri, 25 Jan 2002 15:36:48 -0700 From: Nate Williams <nate@yogotech.com> To: Daniel Eischen <eischen@pcnet1.pcnet.com> Cc: Terry Lambert <tlambert2@mindspring.com>, Dan Eischen <eischen@vigrid.com>, k Macy <kip_macy@yahoo.com>, Peter Wemm <peter@wemm.org>, Julian Elischer <julian@vicor-nb.com>, arch@FreeBSD.ORG Subject: Re: KSE question Message-ID: <15441.56832.170618.611705@caddis.yogotech.com> In-Reply-To: <Pine.SUN.3.91.1020125164325.24428A-100000@pcnet1.pcnet.com> References: <3C51D0B6.F6E04EBC@mindspring.com> <Pine.SUN.3.91.1020125164325.24428A-100000@pcnet1.pcnet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > The FPU usage is problematic, but is also resolvable, as a > > tools issue. > > > > Specifically, if an ELF section were generated whenever > > the compiler generated FPU code (let's call this section > > "flags", for the sake of argument), then the flag "FPU=1" > > could be set there. > > [ ... ] > > Interesting. I think we only care about FPU state > during signal deliver and preemptions though, and in > that case, the kernel can just pass us the "FPU used" > flag and/or "FPU format" along with the interrupted > context. There's lots of talk about using this 'FPU used' flag, but at least my read of things from the long discussion before was that it may not be possible to implement this on the x86 architectures we currently support. It sounds like a great idea, *IF* if can be done. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15441.56832.170618.611705>