https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63172
boger at us dot ibm.com changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--- Comment #6 from boge
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63172
boger at us dot ibm.com changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63172
--- Comment #4 from Dominik Vogt ---
On s390x, the option -fcx-limited-range "fixes" the deviation in the C test
program (tried with -O0 and -O3), but it has no effect for the Go test program.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63172
--- Comment #3 from Dominik Vogt ---
So the problem is that for some targets gcc's constant folding may yield a
different result for floating point calculations than the result if the
calculations were done on the target. The attached test progr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63172
--- Comment #2 from Dominik Vogt ---
Created attachment 33469
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33469&action=edit
Test prog for C
Run with "./mycplx2_c 5 6".
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63172
--- Comment #1 from Dominik Vogt ---
Created attachment 33468
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33468&action=edit
Test prog for Go
Run and watch for differences in the output lines. They should be identical.
