Re: [PATCH 02/10] target/m68k: Avoid using floatx80_infinity global const

2025-02-21 Thread Philippe Mathieu-Daudé
On 17/2/25 13:50, Peter Maydell wrote: The global const floatx80_infinity is (unlike all the other float*_infinity values) target-specific, because whether the explicit Integer bit is set or not varies between m68k and i386. We want to be able to compile softfloat once for multiple targets, so w

Re: [PATCH 02/10] target/m68k: Avoid using floatx80_infinity global const

2025-02-17 Thread Richard Henderson
On 2/17/25 04:50, Peter Maydell wrote: The global const floatx80_infinity is (unlike all the other float*_infinity values) target-specific, because whether the explicit Integer bit is set or not varies between m68k and i386. We want to be able to compile softfloat once for multiple targets, so w

[PATCH 02/10] target/m68k: Avoid using floatx80_infinity global const

2025-02-17 Thread Peter Maydell
The global const floatx80_infinity is (unlike all the other float*_infinity values) target-specific, because whether the explicit Integer bit is set or not varies between m68k and i386. We want to be able to compile softfloat once for multiple targets, so we can't continue to use a single global w