https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93133
rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |rsandifo at gcc dot
gnu.org
--- Comment #3 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org>
---
Mine. TBH I'm not really sure why the AArch64 definition
of REVERSE_CONDITION is there. We can't use CCFP GT as
a form of quiet GT (!UNLT) since it still looks to the
target-independent code like a normal signalling GT,
even if we ever did code-generate it differently.
And there should be no target-specific reasons for
turning a CCFPE GT into a CCFPE UNLT.
So let's see how much breaks if we just remove the
definition. :-)
