Date: Thu, 10 Jan 2002 11:16:33 -0800 From: Terry Lambert <tlambert2@mindspring.com> To: Dan Eischen <eischen@vigrid.com> Cc: Peter Wemm <peter@wemm.org>, Nate Williams <nate@yogotech.com>, Daniel Eischen <eischen@pcnet1.pcnet.com>, Archie Cobbs <archie@dellroad.org>, Alfred Perlstein <bright@mu.org>, arch@FreeBSD.ORG Subject: Re: Request for review: getcontext, setcontext, etc Message-ID: <3C3DE891.99C85D24@mindspring.com> References: <20020110091018.0788A38CC@overcee.netplex.com.au> <3C3D8C47.D3B11B87@vigrid.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Dan Eischen wrote: > I think we determined that the only time we care about the FP state is > when sending a signal. In that case, the kernel should know how to > get the FPU state and copy it out to the context. If there are > different FPU formats, there is a flags word that can be set accordingly > and the userland setcontext() can be made to account for different > floating point formats. > > Currently the kernel doesn't save the FPU state in the sigcontext, > but it should. Wouldn't this solve the problem? What problem? Using FP code in signal handlers isn't legal. Why does everyone want to do Bezier curves in signal handlers? -- Terry 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?3C3DE891.99C85D24>