We only build the PA-RISC targets using big endianness order: $ git grep TARGET_BIG_ENDIAN configs/targets/hppa-* configs/targets/hppa-linux-user.mak:5:TARGET_BIG_ENDIAN=y configs/targets/hppa-softmmu.mak:2:TARGET_BIG_ENDIAN=y
Therefore the MO_TE definition always expands to MO_BE. Use the latter to simplify. Signed-off-by: Philippe Mathieu-Daudé <[email protected]> Reviewed-by: Richard Henderson <[email protected]> Message-Id: <[email protected]> --- target/hppa/translate.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/target/hppa/translate.c b/target/hppa/translate.c index 6fec63cb433..853cba2ba4f 100644 --- a/target/hppa/translate.c +++ b/target/hppa/translate.c @@ -106,7 +106,8 @@ typedef struct DisasContext { static inline MemOp mo_endian(DisasContext *ctx) { - return MO_TE; + /* The PSW_E bit sets the (little) endianness, but we don't implement it. */ + return MO_BE; } /* Note that ssm/rsm instructions number PSW_W and PSW_E differently. */ -- 2.51.0
