Mail Archives: djgpp/1993/04/07/02:25:29
I seem to recall that some users have GCC 2.3.3 running under GO32.
Could somebody try to see if the bug is still present in that version?
These are the .s files using gcc-2.3.3 on a SPARC station II, cross
gcc 2.3.3 snapshot 930305 and gcc-2.3.3 under go32 (using a 386/33 and
wmenu-100) :
***************
double d[] = {
1.0e67,
1.0e68,
1.0e69,
1.0e70,
1.0e71
};
gcc-2.3.3 SPARC : ---------------------------------------
gcc2_compiled.:
.global _d
.data
.align 8
_d:
.double 0r9.9999999999999998e+66
.double 0r9.9999999999999995e+67
.double 0r1.0000000000000001e+69
.double 0r1.0000000000000001e+70
.double 0r1e+71
gcc-2.3.3 snapshot 930305 : -----------------------------
.file "a.c"
gcc2_compiled.:
.globl _d
.data
.align 2
_d:
.double 0d9.99999999999999982737e+66
.double 0d9.99999999999999952805e+67
.double 0d1.00000000000000007253e+69
.double 0d1.00000000000000007253e+70
.double 0d1.00000000000000004188e+71
gcc-2.3.3 under go32 : ----------------------------------
.file "a.c"
gcc2_compiled.:
.globl _d
.data
.align 2
_d:
.double 0d1.00000000000000000000e+67
.double 0d1.00000000000000000000e+68
.double 0d1.00000000000000070000e+69
.double 0d1.00000000000000070000e+70
.double 0d1.00000000000000070000e+71
Isn't that nice. None of the results match :-(
Should be fun to explain that.
There is a new snapshot of gcc on isis.rutgers.edu (930402). I'll try
to build it and try that on it.
Regards,
Rami
- Raw text -