https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118541
--- Comment #8 from Segher Boessenkool ---
(The traditional FP comparisons we do use, i.e. fcmpu. We never used fcmpo,
because it is problematic, it needs access to information that in not in the
RTL at the point of the comparison, that informa
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118541
--- Comment #7 from Segher Boessenkool ---
isgreater is not supposed to set floating point exception flags at all. So
whether the comparison resulted in unordered (i.e., one of the arguments was a
NaN) or not, isgreater should not set VXVC in p
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118541
--- Comment #6 from Michael Meissner ---
I submitted V4 of the patch on March 26th:
https://gcc.gnu.org/pipermail/gcc-patches/2025-March/679428.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118541
--- Comment #5 from Michael Meissner ---
I submitted the patch for this on February 12th, 2025:
https://gcc.gnu.org/pipermail/gcc-patches/2025-February/675616.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118541
Michael Meissner changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |meissner at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118541
--- Comment #3 from Jeevitha ---
(In reply to Florian Weimer from comment #2)
> This is about these glibc test suite failures, right?
>
Yes
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118541
--- Comment #2 from Florian Weimer ---
This is about these glibc test suite failures, right?
FAIL: math/test-double-acospi
FAIL: math/test-float-acospi
FAIL: math/test-float32-acospi
FAIL: math/test-float32x-acospi
FAIL: math/test-float64-acosp
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118541
--- Comment #1 from Jeevitha ---
This issue arises from a glibc math function. Below is the discussion from the
glibc mailing list conversation between Florian and Adhemerval.
I saw this when building for POWER10 and it seems a compiler issue t
