[ppc] Bump (more) instruction sizes after 51c454f6b03b468273bb93db2aa9b76e330a7e57.

This fixes ~30 ppc-specific failures in mono/tests (e.g., appdomain), like this:
	wrong maximal instruction length of instruction atomic_add_i4 (expected 20, got 28)
	* Assertion: should not be reached at mini-ppc.c:5235

The commit 51c454f6b03b468273bb93db2aa9b76e330a7e57 introduced 2 ppc_sync
instructions in OP_ATOMIC_CAS_I4/8 *and* OP_ATOMIC_ADD_NEW_I4/8 (mini-ppc64.c).

Accordingly, commit 83a34c40c6a0911a0c27afce63f5ea7ec2bb4b26 updated the maxlength
(+8 bytes) of atomic_cas_i4/8 - *but not* atomic_add_new_i4/8 (cpu-ppc64.md).

Recently, commit b784b866dac0c97780357bf81bf0fa3ebeffa4e made atomic_add_new_i4/8
exercised (as 'atomic_add_i4/8') - with an incorrect/non-updated 20-byte maxlength,
which should actually be 28.

Thus:
	wrong maximal instruction length of instruction atomic_add_i4 (expected 20, got 28)

Signed-off-by: Mauricio Faria de Oliveira <mauricfo@linux.vnet.ibm.com>

diff --git a/mono/mini/cpu-ppc64.md b/mono/mini/cpu-ppc64.md
index e41064f3afb01727f25ead5d854f17649c517094..bd91b4b88de05ea61376dd7898a89e8f74f4c518 100644 (file)
--- a/mono/mini/cpu-ppc64.md
+++ b/mono/mini/cpu-ppc64.md
@@ -381,7 +381,7 @@ vcall2_membase: src1:b len:16 clob:c
 
 jump_table: dest:i len:20
 
-atomic_add_i4: src1:b src2:i dest:i len:20
-atomic_add_i8: src1:b src2:i dest:i len:20
+atomic_add_i4: src1:b src2:i dest:i len:28
+atomic_add_i8: src1:b src2:i dest:i len:28
 atomic_cas_i4: src1:b src2:i src3:i dest:i len:38
 atomic_cas_i8: src1:b src2:i src3:i dest:i len:38