https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91425
--- Comment #2 from Marc Glisse <glisse at gcc dot gnu.org> --- I think part of the problem with the current or_comparison optimization is that it relies on invert_tree_comparison in many cases, and that doesn't really work for floating point (and we handle the unsafe flags inconsistently, see for instance bug 53806).
