PowerPC regressions in v5.0

[wargio]

1. The ppc_op_crx are not being set in capstone v5 (this applies for X.crx.reg and for X.crx.cond).

The issue is linked to these lines:

• capstone/arch/PowerPC/PPCInstPrinter.c

  Line 350 in 8ae8f68

  MI->flat_insn->detail->ppc.operands[MI->flat_insn->detail->ppc.op_count].reg = MCOperand_getReg(MCInst_getOperand(MI, 1));

• capstone/arch/PowerPC/PPCInstPrinter.c

  Line 131 in 8ae8f68

  static void add_CRxx(MCInst *MI, ppc_reg reg)

2. XORI sometimes is marked as XNOR even if is not XORI r0, r0, 0
3. Some instructions are correctly decoded and their fields are wrongly set:

• Prints rldicl but is set as PPC_INS_CLRLDI.
• Prints rlwinm but is set as PPC_INS_CLRLWI.
• Prints cmpw but is set as PPC_INS_CMP
• Prints cmpd but is set as PPC_INS_CMP
• Prints cmplw but is set as PPC_INS_CMPL
• Prints cmpld but is set as PPC_INS_CMPL
• Prints cmpwi but is set as PPC_INS_CMPI
• Prints cmpdi but is set as PPC_INS_CMPI
• Prints cmplwi but is set as PPC_INS_CMPLI
• Prints cmpldi but is set as PPC_INS_CMPLI

[XVilka]

It doesn't make sense to invest fixing them and it's better to wait for #2013 to get merged if it ever happens

[XVilka]

These regressions could be prevented by running tests on CI for every commit and PR, see #1984

[Rot127]

Mappings are fixed in #2333.

But it is not worth to fix the first point. This is done in the next branch.
So I mark this as wontfix and close it with #2333.

[XVilka]

Should be this closed then? @Rot127