ppc64asm: ignore m[tf]vsr* objdump decoding mismatches

A recent binutils change prioritized extended mnemonics of these
instructions.  These mismatches can be safely ignored.

Fixes golang/go#43222

Change-Id: Ie3df612aad7aaba4798e13bab56b04291c703d48
Reviewed-on: https://go-review.googlesource.com/c/arch/+/278784
Trust: Lynn Boger <laboger@linux.vnet.ibm.com>
Reviewed-by: Cherry Zhang <cherryyz@google.com>
diff --git a/ppc64/ppc64asm/objdump_test.go b/ppc64/ppc64asm/objdump_test.go
index b886f7b..5d48619 100644
--- a/ppc64/ppc64asm/objdump_test.go
+++ b/ppc64/ppc64asm/objdump_test.go
@@ -57,6 +57,8 @@
 		return true
 	case VSPLTB, VSPLTH, VSPLTW: // objdump generates unreasonable result "vspltw v6,v19,4" for 10c49a8c, the last 4 should be 0.
 		return true
+	case MTVSRWA, MTVSRWZ, MFVSRWZ, MFVSRD, MTVSRD: // We don't support extended mnemonics using VRs or FPRs
+		return true
 	if hasPrefix(text, "evm", "evl", "efs") { // objdump will disassemble them wrong (e.g. evmhoumia as vsldoi)
 		return true