target/s390x: don't use ld_code2 to probe next pc

This isn't an translator picking up an instruction so we shouldn't use
the translator_lduw function which has side effects for plugins.

Reviewed-by: David Hildenbrand <david@redhat.com>
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Acked-by: Ilya Leoshkevich <iii@linux.ibm.com>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Message-Id: <20221027183637.2772968-24-alex.bennee@linaro.org>
This commit is contained in:
Alex Bennée 2022-10-27 19:36:29 +01:00
parent 839866fcbd
commit efe7c4f08d
1 changed files with 1 additions and 1 deletions

View File

@ -6612,7 +6612,7 @@ static void s390x_tr_insn_start(DisasContextBase *dcbase, CPUState *cs)
static target_ulong get_next_pc(CPUS390XState *env, DisasContext *s, static target_ulong get_next_pc(CPUS390XState *env, DisasContext *s,
uint64_t pc) uint64_t pc)
{ {
uint64_t insn = ld_code2(env, s, pc); uint64_t insn = cpu_lduw_code(env, pc);
return pc + get_ilen((insn >> 8) & 0xff); return pc + get_ilen((insn >> 8) & 0xff);
} }