[Bug go/63172] gccgo testcase cplx2.go execution provides incorrect answers on trunk for powerpc64, powerpc64le
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63172 boger at us dot ibm.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #5 from boger at us dot ibm.com --- This is the same problem as described in 60181. *** This bug has been marked as a duplicate of bug 60181 ***
[Bug go/63172] gccgo testcase cplx2.go execution provides incorrect answers on trunk for powerpc64, powerpc64le
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 boger at us dot ibm.com --- Comments for this bug will appear in 60181.
[Bug go/63172] gccgo testcase cplx2.go execution provides incorrect answers on trunk for powerpc64, powerpc64le
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63172 --- Comment #4 from Dominik Vogt vogt at linux dot vnet.ibm.com --- 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.
[Bug go/63172] gccgo testcase cplx2.go execution provides incorrect answers on trunk for powerpc64, powerpc64le
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63172 --- Comment #1 from Dominik Vogt vogt at linux dot vnet.ibm.com --- Created attachment 33468 -- https://gcc.gnu.org/bugzilla/attachment.cgi?id=33468action=edit Test prog for Go Run and watch for differences in the output lines. They should be identical.
[Bug go/63172] gccgo testcase cplx2.go execution provides incorrect answers on trunk for powerpc64, powerpc64le
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63172 --- Comment #2 from Dominik Vogt vogt at linux dot vnet.ibm.com --- Created attachment 33469 -- https://gcc.gnu.org/bugzilla/attachment.cgi?id=33469action=edit Test prog for C Run with ./mycplx2_c 5 6.
[Bug go/63172] gccgo testcase cplx2.go execution provides incorrect answers on trunk for powerpc64, powerpc64le
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63172 --- Comment #3 from Dominik Vogt vogt at linux dot vnet.ibm.com --- 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 programs show this for Go and C on s390, and maybe other platforms.
