> If the movcc comparison is not valid it triggers an assert in the > current implementation. This behavior is not needed as we can FAIL > the movcc expand pattern.
In case of a MODE_CC comparison you can also just return it as described here https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104154 or here: https://gcc.gnu.org/pipermail/gcc-patches/2022-February/590639.html If there already is a "CC comparison" the backend does not need to create one and ifcvt can make use of this, creating better sequences. Regards Robin
