Christian Grössler <ch...@groessler.org> writes: > Looking at the history of optabs.c, the MODE_CC test was introduced when > merging the cond-optab branch > to main. I didn't find a description of the cond-optab branch and what it was > supposed to do.
This is the description of the now-merged cond-optab branch, from http://gcc.gnu.org/ml/gcc/2009-04/msg00211.html : This branch is to clean up and simplify the implementation of conditional operations (branches, stores, moves, etc.) in expand and in the machine descriptions. Patches should be marked with the tag [cond-optab] in the subject line. The branch is maintained by Paolo Bonzini. Pending further testing, the branch is ready to be merged into mainline and only bug and documentation fixes should be committed. As I recall the basic idea was to generate all conditional branches via the cbranchMODE4 pattern rather than using separate compare and branch patterns. I couldn't figure out which assertion you hit so I'm not sure what else to say. A const_int is always VOIDmode, and there should be no problem comparing a value to a const_int. Ian
