Re: [PATCH 10/21] target/m68k: Initialize float_status fields in gdb set/get functions

2024-10-28 Thread Richard Henderson
On 10/25/24 15:12, Peter Maydell wrote: In cf_fpu_gdb_get_reg() and cf_fpu_gdb_set_reg() we use a temporary float_status variable to pass to floatx80_to_float64() and float64_to_floatx80(), but we don't initialize it, meaning that those functions could access uninitialized data. Zero-init the st

Re: [PATCH 10/21] target/m68k: Initialize float_status fields in gdb set/get functions

2024-10-25 Thread Philippe Mathieu-Daudé
On 25/10/24 11:12, Peter Maydell wrote: In cf_fpu_gdb_get_reg() and cf_fpu_gdb_set_reg() we use a temporary float_status variable to pass to floatx80_to_float64() and float64_to_floatx80(), but we don't initialize it, meaning that those functions could access uninitialized data. Zero-init the st

[PATCH 10/21] target/m68k: Initialize float_status fields in gdb set/get functions

2024-10-25 Thread Peter Maydell
In cf_fpu_gdb_get_reg() and cf_fpu_gdb_set_reg() we use a temporary float_status variable to pass to floatx80_to_float64() and float64_to_floatx80(), but we don't initialize it, meaning that those functions could access uninitialized data. Zero-init the structs. (We don't need to set a NaN-propag