https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115659
--- Comment #9 from Richard Biener <rguenth at gcc dot gnu.org> --- I think the inversion code wants to check invert_tree_comparison and see if the inverted compare is supported and only if not fall back to inverting the comparison result (there is of course the multi-use case to consider). I also think that incrementally improving the /* Try to fold x CMP y ? -1 : 0 to x CMP y. */ is fine we don't have to handle everything in one patch. Thanks for working on this. The x86 folks seem to be able to handle most things within the backend which is also fine, handling common problems in the middle-end is of course better.
