https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119629
--- Comment #10 from Alexandre Oliva <aoliva at gcc dot gnu.org> --- >> - instructions and expanders for these builtins don't have their conditions >> tested, so they must necessarily follow from the builtin conditions, and >> this case clearly isn't > "They don't have their conditions tested"? What does that mean? It means that the code that introduces the builtins checks the conditions of the builtin set, not the conditions of the insn expander, so they must match, but they don't. >> - TARGET_MODULO isn't used very often in conditions in the .md file, but it >> can be controlled independently from TARGET_P9_MISC > Yes? What is the question? If one were to compile with -mno-p9-misc -mmodulo, the builtin would be enabled, but its expansion would ICE because the insn conditions are not met. That's a variant of the -mpowerpc64/-m64 condition mismatch fixed in the patch in comment 2.
