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 0B5EF3858C41; Wed, 28 Feb 2024 01:55:29 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0B5EF3858C41
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1709085330;
	bh=oFCUQOxNA54igukJTmltpdo2Kz8pZkzgqi03ZZ7hgRs=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=fIh30CAR8p+og9FFc4TRkyJR9ovi3MYIh+/PuTEN0aQ52MvSCH8IFfaP/dDmXgkVI
	 C8Ksl/ywf/oT3mvX/cMO6zLdAXWSpvNPCHdZG0cMtqklHDs9bSHSOySxY5GEKvvvV0
	 bfJql3VXHI2hIAAQuMFdVJNNuwHUcODlTbEvFVNE=
From: "g.peterhoff@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libquadmath/114140] different results for std::fmin/std::fmax
 and quadmath fminq/fmaxq if one argument=signaling_NaN
Date: Wed, 28 Feb 2024 01:55:29 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libquadmath
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: g.peterhoff@t-online.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: 
Message-ID: <bug-114140-4-xTZJ5yGK8G@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-114140-4@http.gcc.gnu.org/bugzilla/>
References: <bug-114140-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=3D114140

--- Comment #13 from g.peterhoff@t-online.de ---
> The cppreference page is wrong.
But then *all* of your implementations for fmin/fmax (float, double, long
double, std::floatN_t) would be wrong, because they give exactly the result=
s as
described on cppreference.
Is this really the case (which I don't believe)? And if so, that still does=
n't
solve the original problem: std::math-functions and quadmath-functions *mus=
t*
of course return the same results - no matter which implementation is corre=
ct.=