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 CA6F4385086C; Wed,  7 Sep 2022 10:06:45 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org CA6F4385086C
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1662545205;
	bh=ui4/h7UFe5tjxMuMciq6k8wYgl8vtQnnA3/jgEzIht0=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=cdqXXc4JL3ut/ojI8lnGUkW/Nu/Q/ZTjJy4Qgh+w8CfC0G7iqm8RJdZoMRVNSVLjA
	 Y2neNbmxyufXV58Ysa9Qy/7JwzS7/332M1rK330C0yjTXX0fHjXLNwNr77WZqnzsGp
	 VDZwm/p1mlV1wfnojT7O/x0W+LHK79QE/EDtlj/I=
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/55522] -funsafe-math-optimizations is unexpectedly
 harmful, especially w/ -shared
Date: Wed, 07 Sep 2022 10:06:44 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 4.6.3
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: major
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: NEW
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: 
Message-ID: <bug-55522-4-NjdPanvT5F@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-55522-4@http.gcc.gnu.org/bugzilla/>
References: <bug-55522-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=3D55522

--- Comment #15 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #13)
> Patient: Doctor it hurts when I do this.
> Doctor: then don't do that and if you read the instructions I gave you I
> told you I would hurt this way.
>=20

The problem I see with this analogy, is who exactly is the doctor in this
situation? It seems that currently the doctor is the GCC devs, but I think =
the
situation could be improved by having GCC itself be the doctor, by implemen=
ting
a -Wfast-math warning flag or something to make the issues with -ffast-math
more known. Having it documented in the instructions is just one place; it
should be mentioned in all the relevant places that a user might check.=