https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91425
--- Comment #12 from Drea Pinski <pinskia at gcc dot gnu.org> --- I have to think about the full fix. == returns false for nans. U> returns false for nan. Unlike >. So if we have a || b where a was !(u) if b is trapping then this would be true also for nans. If a was !(t) then this would turn into u which was false but then b being trapping would would be ok too. As long as we get trapping back, I think it would not. So for signaling nans, the we should not allow the conversion. For a&&b, if a was !(t) than that turns into u . We need to get a trapping version back but I am not positive it would.
