public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
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 [thread overview] Message-ID: <bug-26045-131-3Rnv4KIFZg@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-26045-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=26045 --- 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 (the high bit of the significand is 0), meaning that fmaxf (which corresponds to maxNum from IEEE 754-2008, *not* to one of the newer operations from IEEE 754-2019) is correct to raise "invalid" and return a signaling NaN. x86_64 is little-endian, so -3(%rsp) has less-significant bits than -2(%rsp). -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2020-06-01 22:52 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-26 12:43 [Bug math/26045] New: " florian at schanda dot org.uk 2020-05-27 9:59 ` [Bug math/26045] " amonakov at gmail dot com 2020-06-01 22:52 ` joseph at codesourcery dot com [this message] 2020-06-02 6:18 ` amonakov at gmail dot com 2020-06-02 13:59 ` joseph at codesourcery dot com 2021-09-29 16:19 ` jsm28 at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-26045-131-3Rnv4KIFZg@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).