target-m68k: Remove incorrect clearing of cc_x

The CF docs certainly doesnt suggest this is true.

Signed-off-by: Richard Henderson <rth@twiddle.net>
Signed-off-by: Laurent Vivier <laurent@vivier.eu>
This commit is contained in:
Richard Henderson 2015-08-14 07:59:18 -07:00 committed by Laurent Vivier
parent 99c514485b
commit 18dd87f26b
1 changed files with 0 additions and 7 deletions

View File

@ -207,19 +207,12 @@ static uint32_t cpu_m68k_flush_flags(CPUM68KState *env, int op)
break;
case CC_OP_LOGICB:
SET_NZ(dest, int8_t);
goto set_x;
break;
case CC_OP_LOGICW:
SET_NZ(dest, int16_t);
goto set_x;
break;
case CC_OP_LOGIC:
SET_NZ(dest, int32_t);
set_x:
if (!m68k_feature(env, M68K_FEATURE_M68000)) {
/* Unlike m68k, coldfire always clears the overflow bit. */
env->cc_x = 0;
}
break;
case CC_OP_ADDB:
SET_FLAGS_ADD(int8_t, uint8_t);