Re: [PATCH 07/10] fpu: Always decide no_signaling_nans() at runtime

2025-02-17 Thread Richard Henderson
On 2/17/25 04:50, Peter Maydell wrote: Currently we have a compile-time shortcut where we return false from no_signaling_nans() on everything except Xtensa, because we know that's the only target that might ever set status->no_signaling_nans. Remove the ifdef, so we always look at the status fla

Re: [PATCH 07/10] fpu: Always decide no_signaling_nans() at runtime

2025-02-17 Thread Philippe Mathieu-Daudé
On 17/2/25 13:50, Peter Maydell wrote: Currently we have a compile-time shortcut where we return false from no_signaling_nans() on everything except Xtensa, because we know that's the only target that might ever set status->no_signaling_nans. Remove the ifdef, so we always look at the status fla

[PATCH 07/10] fpu: Always decide no_signaling_nans() at runtime

2025-02-17 Thread Peter Maydell
Currently we have a compile-time shortcut where we return false from no_signaling_nans() on everything except Xtensa, because we know that's the only target that might ever set status->no_signaling_nans. Remove the ifdef, so we always look at the status flag; this has no behavioural change, but wi