[Bug target/84366] gcc.dg/torture/float128-cmp-invalid.c fails when run on power9

2018-03-26 Thread segher at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84366 Segher Boessenkool changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug target/84366] gcc.dg/torture/float128-cmp-invalid.c fails when run on power9

2018-02-13 Thread meissner at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84366 Michael Meissner changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug target/84366] gcc.dg/torture/float128-cmp-invalid.c fails when run on power9

2018-02-13 Thread joseph at codesourcery dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84366 --- Comment #3 from joseph at codesourcery dot com --- All ordered comparisons (< <= > >=) with at least one argument NaN should raise invalid, so it's indeed just one case of bug 58684.

[Bug target/84366] gcc.dg/torture/float128-cmp-invalid.c fails when run on power9

2018-02-13 Thread segher at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84366 --- Comment #2 from Segher Boessenkool --- Oh wait, this one is comparing 0. to NaN, not the same thing?

[Bug target/84366] gcc.dg/torture/float128-cmp-invalid.c fails when run on power9

2018-02-13 Thread segher at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84366 --- Comment #1 from Segher Boessenkool --- This is just the ieee128 variant of PR58684, right?