Peter Maydell 1839189bbf softfloat: Handle default NaN mode after pickNaNMulAdd, not before ... It is implementation defined whether a multiply-add of (0,inf,qnan) or (inf,0,qnan) raises InvalidaOperation or not, so we let the target-specific pickNaNMulAdd function handle this. This means that we must do the "return the default NaN in default NaN mode" check after the call, not before. Correct the ordering, and restore the comment from the old propagateFloat64MulAddNaN() that warned about this corner case. This fixes a regression from 2.11 for Arm guests where we would incorrectly fail to set the Invalid flag for these cases. Cc: qemu-stable@nongnu.org Signed-off-by: Peter Maydell <peter.maydell@linaro.org> Reviewed-by: Richard Henderson <richard.henderson@linaro.org> Reviewed-by: Alex Bennée <alex.bennee@linaro.org> Tested-by: Alex Bennée <alex.bennee@linaro.org> Message-id: 20180504100547.14621-1-peter.maydell@linaro.org		2018-05-10 18:10:56 +01:00
..
softfloat-specialize.h	RISC-V FPU Support	2018-03-07 08:30:28 +13:00
softfloat.c	softfloat: Handle default NaN mode after pickNaNMulAdd, not before	2018-05-10 18:10:56 +01:00