On 28 January 2015 at 15:40, Xiangyu Hu <libhu...@gmail.com> wrote: > While FMULX returns a 2.0f float when two operators are infinity and > zero, those operators should be unpacked from raw inputs first. Inconsistent > cases would occur when operators are denormalized floats in flush-to-zero > mode. A wrong codepath will be entered and 2.0f will not be returned > without this patch. > Fix by checking whether inputs need to be flushed before running into > different codepaths. > > Signed-off-by: Xiangyu Hu <libhu...@gmail.com>
Applied to target-arm.next, thanks. It looks like we have equivalent bugs in the FRECPS and FRSQRTS instructions... -- PMM
