Commit 95256e5d50 for qemu.org

commit 95256e5d503d11e6163fd7f0d58a478ca7ebe099
Author: Matt Turner <mattst88@gmail.com>
Date:   Mon May 25 11:26:42 2026 -0400

    target/sh4: sync fp_status when gdb writes FPSCR

    sh4_cpu_gdb_write_register() wrote the incoming FPSCR value straight
    into env->fpscr, leaving the derived env->fp_status (rounding mode and
    flush-to-zero) stale, so a gdb-initiated FPSCR change did not take
    effect for subsequent FP operations. Use cpu_load_fpscr() instead, the
    same way the adjacent case already uses cpu_write_sr() for SR.

    Cc: qemu-stable@nongnu.org
    Reviewed-by: Yoshinori Sato <yoshinori.sato@nifty.com>
    Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
    Signed-off-by: Matt Turner <mattst88@gmail.com>
    Signed-off-by: Helge Deller <deller@gmx.de>

diff --git a/target/sh4/gdbstub.c b/target/sh4/gdbstub.c
index 4f36e800d2..bdc8c1d164 100644
--- a/target/sh4/gdbstub.c
+++ b/target/sh4/gdbstub.c
@@ -113,7 +113,7 @@ int superh_cpu_gdb_write_register(CPUState *cs, uint8_t *mem_buf, int n)
         env->fpul = ldl_p(mem_buf);
         break;
     case 24:
-        env->fpscr = ldl_p(mem_buf);
+        cpu_load_fpscr(env, ldl_p(mem_buf));
         break;
     case 25 ... 40:
         if (env->fpscr & FPSCR_FR) {