Mail Archives: djgpp/1998/11/15/12:30:23
> > This is a known problem in some environments. The DJGPP startup code
> > doesn't clear the FPU and leaves the Invalid exception unmasked. So when
> > a previous program left the FPU in a mess, and the OS didn't clean up (I
> > think Windows is sloppy in this regard), the next program crashes during
> > startup.
> Now, it seems to me I've asked this before, but I've forgotten the
> answer. Why don't we reset the FPU at startup, shutdown, or in the
> default SIGFPR handler?
Actually we do reset the FPU at startup during the detection phase. The
problem noted is a bug in Windows which only appears when certain software
is installed on the machine which changes it's behavior. There is no
workaround for this - we've tried - the only fix is to remove the software
on that particular machine which is breaking Windows. This is NOT a
DJGPP problem ...
- Raw text -