X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
Date: Wed, 18 Feb 2004 20:46:49 +0200
From: "Eli Zaretskii" <eliz AT elta DOT co DOT il>
Sender: halo1 AT zahav DOT net DOT il
To: djgpp AT delorie DOT com
Message-Id: <3791-Wed18Feb2004204649+0200-eliz@elta.co.il>
X-Mailer: emacs 21.3.50 (via feedmail 8 I) and Blat ver 1.8.9
In-reply-to: <403391FA.119903C6@yahoo.com> (message from CBFalconer on Wed, 18
	Feb 2004 17:06:08 GMT)
Subject: Re: Cross Platform Incompatabilites? - code fragments
References: <3 DOT 0 DOT 1 DOT 16 DOT 20040216231142 DOT 38e7a7cc AT earthlink DOT net> <c0t2ef$gsf$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE> <2719-Tue17Feb2004213034+0200-eliz AT elta DOT co DOT il> <c0vftb$5ft$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE> <ud68c4g4f DOT fsf AT elta DOT co DOT il> <403391FA DOT 119903C6 AT yahoo DOT com>
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> From: CBFalconer <cbfalconer AT yahoo DOT com>
> Newsgroups: comp.os.msdos.djgpp
> Date: Wed, 18 Feb 2004 17:06:08 GMT
> > 
> > I thought about something like that, but this could only have
> > effect on programs that trigger exceptions, no?
> 
> Such as events triggered by the timers, giving time slices to
> other processes, etc.

I don't think so.  Do you have examples?

A multitasking, multiprocessing OS should save and restore the state
of the FPU between context switches.  IIRC, Windows indeed does that,
except in the exceptional conditions, when a program triggered an FP
exception in the x87.  That's why I suggested, at the beginning of
this thread, to turn on the SIGFPE generation (it is usually masked
off by the DJGPP startup code).  The OP replied that doing so didn't
make any difference, so it seems like this problem is not the reason
for the different behavior.

Hans-Bernhard also mentioned the effects on the FPU precision, but I
don't think this could be relevant unless the program in point fiddles
with the default precision of the FPU, which I think is not the case.