🚀 go-pugleaf

There is a floating point comparison problem with the C compiler, resulting
from the  interaction of compiler switches  with the 68040 CPU. If  you run
this program through /NeXTStep_3.0/bin/cc (July 21, 1992):

	#include <stdio.h>
	int main() {
	  double omega;  double decay= 0.02, rev=0.05;
	
	  fprintf(stderr, "Code Starts");  omega = (rev)/(decay);

	  fprintf(stderr, "\n OMEGA = %f ==> %d\n", omega, omega!=omega);
	  fprintf(stderr, " OMEGA = %f ==> %d\n", omega, omega!=omega);
	  fprintf(stderr, " OMEGA = %f ==> %d\n", omega, omega!=omega);
	}

the output is

	Code Starts
	 OMEGA = 2.500000 ==> 1
	 OMEGA = 2.500000 ==> 0
	 OMEGA = 2.500000 ==> 0

If you use #define isNaN(x) ((x)!=(x)), chances  are your  code may produce
incorrect results.

The cure is to use the compiler switch -m68040-only (on  the C compiler) or
-ffloat-store (either on the C or the C++ compiler).   (I believe the cause
of  the    problem  is  how  differences in   internal  and external/stored
precisions interact with  compiler optimizations.)  Of course, your  MFLOPS
rating may go down...

/ivo welch