Build warning on TOT

Anyone seeing the following:

llvm[3]: Compiling SelectionDAGISel.cpp for Release+Asserts build
Decoding Conflict:
    ____0001111_........________....
    ____0001111_....................
    ____0001111.....................
    ____0001..1.....................
    ____0001........................
    ____00..........................
    ____............................
    ................................
  MVNCCi ____0001111_____________________
  MVNs ____0001111_____________________

Cameron Esfahani
dirty@apple.com

"All that is necessary for the triumph of evil is that good men do nothing."

Yes, and it's a recent regression. Building without -j shows where it really is:

llvm[3]: Building ARM.td decoder tables with tblgen
Decoding Conflict:
     ____0001111_........________....
     ____0001111_....................
     ____0001111.....................
     ____0001..1.....................
     ____0001........................
     ____00..........................
     ____............................
     ................................
   MVNCCi ____0001111_____________________
   MVNs ____0001111_____________________
llvm[3]: Building ARM.td enhanced disassembly information with tblgen

Yes, and it's a recent regression. Building without -j shows where it
really is:

llvm[3]: Building ARM.td decoder tables with tblgen
Decoding Conflict:
    ____0001111_........________....
    ____0001111_....................
    ____0001111.....................
    ____0001..1.....................
    ____0001........................
    ____00..........................
    ____............................
    ................................
  MVNCCi ____0001111_____________________
  MVNs ____0001111_____________________
llvm[3]: Building ARM.td enhanced disassembly information with tblgen

This is almost certainly bill's r 112664 patch. Bill, please take a look. If you need to pattern match something to MVN, you should define it in terms of a Pat<> pattern, not a new synonym for the same instruction.

-Chris

(Late reply) I'm looking into this and the resulting failure(s) introduced by the patch. All shall be fixed but almost certainly after the 2.8 branch.

-bw