On Mon, May 25, 2026 at 11:26 AM Matt Turner <[email protected]> wrote: > > 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: [email protected] > ---
Signed-off-by: Matt Turner <[email protected]>
