From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 31D7A3865C23; Thu, 27 Oct 2022 15:27:09 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 31D7A3865C23
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1666884429;
	bh=hkhE7sAg0/sCIzvFvkQscKFJ3yUOmIxy7n8o17C7H7w=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=X17nJCmmGPXQQrSEBN+1kjZwGt6CfDRoWst1DVPAXHi1+Ux90lwZ3Wemd1c2LDXbD
	 1hQt+25C+6zRtllqNpmJ/RwR2Nxnw6MxzEt6v/SGm4HOj/iGmhqZMfw8rg6cB5c9VZ
	 K9+uzuhsTkqyou2MOYsY6hyAraskF8zAs4I55IVY=
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/107436] Is -fsignaling-nans still experimental?
Date: Thu, 27 Oct 2022 15:27:08 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: see_also
Message-ID: <bug-107436-4-7r9suW0hv2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-107436-4@http.gcc.gnu.org/bugzilla/>
References: <bug-107436-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D107436

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |https://gcc.gnu.org/bugzill
                   |                            |a/show_bug.cgi?id=3D57994,
                   |                            |https://gcc.gnu.org/bugzill
                   |                            |a/show_bug.cgi?id=3D67052,
                   |                            |https://gcc.gnu.org/bugzill
                   |                            |a/show_bug.cgi?id=3D77926,
                   |                            |https://gcc.gnu.org/bugzill
                   |                            |a/show_bug.cgi?id=3D88640,
                   |                            |https://gcc.gnu.org/bugzill
                   |                            |a/show_bug.cgi?id=3D97965,
                   |                            |https://gcc.gnu.org/bugzill
                   |                            |a/show_bug.cgi?id=3D52258,
                   |                            |https://gcc.gnu.org/bugzill
                   |                            |a/show_bug.cgi?id=3D46993

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
There seems like there are still known issues with signalling nans on diffe=
rent
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 ...=