From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 7D3293846446; Thu, 27 Oct 2022 15:17:53 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 7D3293846446 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1666883873; bh=kPD3+r0/4NJ0V1uMjypvQmwoBzpdDkTtSwSrzSz/imk=; h=From:To:Subject:Date:From; b=FYBw1dN8KJd0SifC7CX9mBJWgh80A8iVwo4ZzZCKw4mXkQcgaGrlo6K/fC2zzRYpL 77hr2yQ6sFfaB94kUYTcc+KlEjjd5zFX/f4UN/rCZzOxWzUYzFJzG5mKVn+Poc6W0R rKf46Qsfwq/O/Hq85V+BE5wde8xM6wImEKjvQpYo= From: "florian.schanda at bmw dot de" To: gcc-bugs@gcc.gnu.org Subject: [Bug web/107436] New: Is -fsignaling-nans still experimental? Date: Thu, 27 Oct 2022 15:17:52 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: web X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: florian.schanda at bmw dot de 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D107436 Bug ID: 107436 Summary: Is -fsignaling-nans still experimental? Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: web Assignee: unassigned at gcc dot gnu.org Reporter: florian.schanda at bmw dot de Target Milestone: --- Hi, Is the following statement in the documentation on "-fsignaling-nans" still correct? > This option is experimental and does not currently guarantee to > disable all GCC optimizations that affect signaling NaN behavior. The context is that we have a safety mechanism in a third-party library that relies signalling nans to work correctly; and if we cannot guarantee=20 it with this option it would be a major headache indeed. Any advice (or even better statement that the experimental note is outdated and can be deleted) would be appreciated. Many thanks in advance!=