https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107436
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=57994,
| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=67052,
| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=77926,
| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=88640,
| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=97965,
| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=52258,
| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=46993
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
There seems like there are still known issues with signalling nans on different
targets still. There has been many fixes in recent years but not all might be
there.
Also it depends on the target you are targetting.
A third party library depending on signaling NaNs is slightly an issue in
general considering -fsignaling-nans is not on by default and some (many?)
targets fpu have issues with signaling NaNs in general ...
