X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f From: Hans-Bernhard Broeker Newsgroups: comp.os.msdos.djgpp Subject: Re: Cross Platform Incompatabilites? - code fragments Date: 18 Feb 2004 19:26:25 GMT Organization: Aachen University of Technology (RWTH) Lines: 22 Message-ID: References: <3 DOT 0 DOT 1 DOT 16 DOT 20040216231142 DOT 38e7a7cc AT earthlink DOT net> <2719-Tue17Feb2004213034+0200-eliz AT elta DOT co DOT il> <403391FA DOT 119903C6 AT yahoo DOT com> <3791-Wed18Feb2004204649+0200-eliz AT elta DOT co DOT il> NNTP-Posting-Host: ac3b07.physik.rwth-aachen.de X-Trace: nets3.rz.RWTH-Aachen.DE 1077132385 12760 137.226.33.205 (18 Feb 2004 19:26:25 GMT) X-Complaints-To: abuse AT rwth-aachen DOT de NNTP-Posting-Date: 18 Feb 2004 19:26:25 GMT To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Eli Zaretskii wrote: > 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. My point was that some *other* part of the environment may be twiddling the default precision of the FPU here. It may be the FPU configuration inherited from the environment at program start that's different. More hypothetically, the configuration might even change during runtime. If this were the root of the problem at hand, the fact that the program under study doesn't change the FPU's precision control would contribute to the problem, rather than help solving it. I am going out on a long limb here, but without feedback from the OP, that's the best we can do. -- Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de) Even if all the snow were burnt, ashes would remain.