Date: Tue, 21 Nov 1995 11:12:39 -0700 (MST) From: Terry Lambert <terry@lambert.org> To: cimaxp1!jb@werple.net.au (John Birrell) Cc: terry@lambert.org, hackers@FreeBSD.org, jb@cimlogic.com.au Subject: Re: int type in jmpbuf Message-ID: <199511211812.LAA04316@phaeton.artisoft.com> In-Reply-To: <199511210106.MAA29490@werple.net.au> from "John Birrell" at Nov 21, 95 12:10:30 pm
next in thread | previous in thread | raw e-mail | index | archive | help
[ ... preeemptive thread scheduling using signals ... ] > > If you need it, you should add a system call (like SunOS has) to save > > and restore register state, including the FP registers. > > We're doing as the MIT pthreads code does (__asm__ fsave/frstor) to save and > restore the FP state on entering the scheduler from the real signal handler. > So far we don't see a problem on the 486 we are using. It's the coprocessor > problem that Bruce was pointing out that we can't cope with. We're treating > that as a limitation and pressing on... As long as you are hacking, putting the state save/restore for the signal handler below a system call interface would save your portability to non x86 platforms. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199511211812.LAA04316>