From 18dd87f26bed46f22bb1b9536329c02de500f407 Mon Sep 17 00:00:00 2001 From: Richard Henderson Date: Fri, 14 Aug 2015 07:59:18 -0700 Subject: target-m68k: Remove incorrect clearing of cc_x The CF docs certainly doesnt suggest this is true. Signed-off-by: Richard Henderson Signed-off-by: Laurent Vivier --- target-m68k/helper.c | 7 ------- 1 file changed, 7 deletions(-) (limited to 'target-m68k/helper.c') diff --git a/target-m68k/helper.c b/target-m68k/helper.c index 1a54e6678b..a9974b1b73 100644 --- a/target-m68k/helper.c +++ b/target-m68k/helper.c @@ -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); -- cgit v1.2.3