From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: [musl] Min and Max of 2 Floating Point numbers
Date: Sun, 23 Feb 2020 10:21:47 -0500 [thread overview]
Message-ID: <20200223152147.GO1663@brightrain.aerifal.cx> (raw)
In-Reply-To: <alpine.LRH.2.02.2002231724010.23908@key0.esi.com.au>
On Sun, Feb 23, 2020 at 06:08:25PM +1100, Damian McGuckin wrote:
> The IEEE 754-2019 standard has changed the definition so as to
> properly propogate NaNs. The 1.2.0 version I just downloaded still
> follows the
> 2008 definition.
>
> ARM is smart enough to have 2 instructions, one (FMAX) which did
> propogate NaNs and one (FMAXNM) which follows the 2008 standard.
> That said, I do not personally compile on an ARM so I have no idea
> how you ask for FMAX or how you ask for FMAXNM?
>
> The PowerPC ISA 3.0 instruction properly propogates NaNs so it
> agrees with the new standard.
>
> The Intel instruction follows neither standard as far as I can tell. An
> interesting condition.
>
> Please tell me if I am wrong.
I'm not particularly aware of what the insns do. However..
> MUSL relevance: I believe that even in 1.2.0, MUSL's own fmax/fmin libc
> routines violate the IEEE 754-2019 standard which came out recently.
> Well, it was approved June, published July, released November. I
> think that is recent.
Unless by "propagate nans" you mean some specific behavior beyond
preserving one of the input nans, I don't see how we're violating it.
The < operator is only used if there are no nans and the signs are the
same.
Rich
next prev parent reply other threads:[~2020-02-23 15:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-23 7:08 Damian McGuckin
2020-02-23 15:21 ` Rich Felker [this message]
2020-02-23 21:03 ` Damian McGuckin
2020-02-23 21:18 ` Florian Weimer
2020-02-23 23:20 ` Damian McGuckin
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=20200223152147.GO1663@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).