search for: convertmethod

...ally) be wider than just disassembly. For example we will eventually want to reject some load instructions based on complex operand constraints (e.g. if it's write-back indexed and Rt == Rn). Currently the only way to handle cross-operand conditions in the AsmParser (I believe) is with a custom ConvertMethod, which is even more heavyweight than the disassembler situation. I think making this checker work for assembly would be rather simple if the method acts on an MCInst, but probably not possible if it also gets to use the bit-pattern as suggested. In addition, in my view working on the bit-pattern...

Hello. Sometimes the constraints imposed on an instruction's encoding are too complex to be described in tablegen alone. In such cases a custom decoder method is implemented. This makes sense when the decoding itself is very complex, but it is wasteful to do it only when checking additional constraints. This is because: 1. a custom decoder method has to decode operands, set opcodes, etc. -