From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
 id 46D4B3840C16; Mon,  1 Jun 2020 22:52:56 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 46D4B3840C16
From: "joseph at codesourcery dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug math/26045] fmaxf(inf, nan) does not always work
Date: Mon, 01 Jun 2020 22:52:56 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: math
X-Bugzilla-Version: 2.28
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: joseph at codesourcery dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-26045-131-3Rnv4KIFZg@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-26045-131@http.sourceware.org/bugzilla/>
References: <bug-26045-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: glibc-bugs@sourceware.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Glibc-bugs mailing list <glibc-bugs.sourceware.org>
List-Unsubscribe: <http://sourceware.org/mailman/options/glibc-bugs>,
 <mailto:glibc-bugs-request@sourceware.org?subject=unsubscribe>
List-Archive: <https://sourceware.org/pipermail/glibc-bugs/>
List-Help: <mailto:glibc-bugs-request@sourceware.org?subject=help>
List-Subscribe: <http://sourceware.org/mailman/listinfo/glibc-bugs>,
 <mailto:glibc-bugs-request@sourceware.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Jun 2020 22:52:56 -0000

https://sourceware.org/bugzilla/show_bug.cgi?id=3D26045

--- Comment #2 from joseph at codesourcery dot com <joseph at codesourcery =
dot com> ---
I don't see a bug here.  That specially crafted NaN is a signaling NaN=20
(the high bit of the significand is 0), meaning that fmaxf (which=20
corresponds to maxNum from IEEE 754-2008, *not* to one of the newer=20
operations from IEEE 754-2019) is correct to raise "invalid" and return a=20
signaling NaN.  x86_64 is little-endian, so -3(%rsp) has less-significant=20
bits than -2(%rsp).

--=20
You are receiving this mail because:
You are on the CC list for the bug.=