From: Philippe Mathieu-Daudé Date: Wed, 8 Oct 2025 06:15:23 +0000 (+0200) Subject: target/loongarch: Remove target_ulong use in gdb_write_register handler X-Git-Tag: v10.2.0-rc1~61^2~61 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=7f306758fb83f1b64d02647171d5f65fc157ac25;p=thirdparty%2Fqemu.git target/loongarch: Remove target_ulong use in gdb_write_register handler ldq_le_p() returns a uint64_t type, big enough to also hold ldl_le_p() return value. If we were building for a 32-bit LoongArch target, ldq_le_p() would not fit in target_ulong. Better stick to plain uint64_t. Signed-off-by: Philippe Mathieu-Daudé Reviewed-by: Richard Henderson Reviewed-by: Song Gao Message-Id: <20251009201947.34643-4-philmd@linaro.org> --- diff --git a/target/loongarch/gdbstub.c b/target/loongarch/gdbstub.c index 471eda28c7..23a5eecc20 100644 --- a/target/loongarch/gdbstub.c +++ b/target/loongarch/gdbstub.c @@ -62,7 +62,7 @@ int loongarch_cpu_gdb_read_register(CPUState *cs, GByteArray *mem_buf, int n) int loongarch_cpu_gdb_write_register(CPUState *cs, uint8_t *mem_buf, int n) { CPULoongArchState *env = cpu_env(cs); - target_ulong tmp; + uint64_t tmp; int length = 0; if (n < 0 || n > 34) {