This adds a bunch of OPERAND_MEMORY OperandTypes around the memory operands (addrmode & friends).
I'm pretty sure this can't affect anything in-tree, but not 100%, hence this thread. This also makes this all pretty much untestable. The OperandType users are mostly disassemblers and similar tools; more information is helpful for those.
Some of the PC-relative things, I'm on the fence (e.g. addrmodepc, t2adrlabel, t_adrlabel, and the various *ld*pcrel*). OPERAND_PCREL sounds better, but in practice, I know some OperandType users interpret "PCREL" as labels and other code-related pointers, so OPERAND_MEMORY is more suitable, really. Basically, the names are a tad misleading.
Thanks!
-Ahmed
What is the rational behind the non-consistent uses of MemOperand and let OperandType = “OPERAND_MEMORY"?