Date: Tue, 21 Nov 1995 12:10:30 +1100 (EST) From: John Birrell <cimaxp1!jb@werple.net.au> To: lambert.org!terry@werple.net.au (Terry Lambert) Cc: hackers@FreeBSD.org, jb@cimlogic.com.au Subject: Re: int type in jmpbuf Message-ID: <199511210106.MAA29492@werple.net.au> In-Reply-To: <199511210032.RAA02606@phaeton.artisoft.com> from "Terry Lambert" at Nov 20, 95 05:32:13 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > two threads each doing while(1); ?? > > Shoot the programmer. 8-). Attempted suicide is against the law here - I'm a rotten shot. 8-). > > Seriously, nothing requires that the scheduling of threads be preemptive. We have process control software that runs really nicely with preemptive time slicing. I'll concede that its not _required_, but I like the way the software runs as is. > > 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... > > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. > -- John Birrell CIMlogic Pty Ltd jb@cimlogic.com.au 119 Cecil Street Ph +61 3 9690 9600 South Melbourne Vic 3205 Fax +61 3 9690 6650 Australia Mob +61 18 353 137
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199511210106.MAA29492>