public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug math/26045] fmaxf(inf, nan) does not always work
Date: Wed, 29 Sep 2021 16:19:21 +0000 [thread overview]
Message-ID: <bug-26045-131-J0i15oSmK6@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26045-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=26045
Joseph Myers <jsm28 at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|UNCONFIRMED |RESOLVED
Target Milestone|--- |2.35
--- Comment #5 from Joseph Myers <jsm28 at gcc dot gnu.org> ---
I updated the documentation of fmax and fmin to mention the signaling NaN
semantics as part of:
commit 90f0ac10a74b2d43b5a65aab4be40565e359be43
Author: Joseph Myers <joseph@codesourcery.com>
Date: Tue Sep 28 23:31:35 2021 +0000
Add fmaximum, fminimum functions
So there was nothing to do for this issue all along as regards the code, and
now the documentation addresses the sNaN issue for these functions properly as
well.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2021-09-29 16:19 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
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 [this message]
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-J0i15oSmK6@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: link
Be 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).