https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106831
Aldy Hernandez <aldyh at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #1 from Aldy Hernandez <aldyh at gcc dot gnu.org> ---
Should be fixed with:
commit 8293a9632c46c8f3f9d531c09194aa8738944927
Author: Aldy Hernandez <al...@redhat.com>
Date: Sun Sep 4 08:00:02 2022 +0200
Do not clobber signbit when unioning a NAN.
When unioning a known NAN and something else, we're dropping the
properties of the NAN, particularly the sign. This fixes the
oversight.
With this patch, we should be keeping the sign bit up to date, even in
the presence of NANs.
and this:
commit dae8b9e2bbb6017bf90d68c7b720c500125c8295
Author: Aldy Hernandez <al...@redhat.com>
Date: Sat Sep 3 15:41:06 2022 +0200
[PR/middle-end 106819] NANs can never be a singleton
Possible NANs can never be a singleton, so they will never be
propagated. This was the intent, and then the signed zero code crept
in, and was mistakenly checked before the NAN.
