From: Joseph Myers <joseph@codesourcery.com>
To: FX <fxcoudert@gmail.com>
Cc: Jakub Jelinek <jakub@redhat.com>, <gcc@gcc.gnu.org>,
FX via Fortran <fortran@gcc.gnu.org>
Subject: Re: Floating-point comparisons in the middle-end
Date: Thu, 1 Sep 2022 19:16:50 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2209011913500.550568@digraph.polyomino.org.uk> (raw)
In-Reply-To: <2C40E85D-1B5B-47C4-A855-910102CABCA3@gmail.com>
On Thu, 1 Sep 2022, FX via Gcc wrote:
> The next thing I need to tackle for Fortran is the implementation of
> functions that perform maxNum, maxNumMag, minNum, and minNumMag. Am I
> correct in assuming that maxNum and minNum correspond to fmin and fmax?
Yes (note that maxNum and minNum were removed in IEEE 754-2019, but
they're still what fmax and fmin correspond to; the new minimum / maximum
operations in IEEE 754-2019 are provided by new functions in C2x).
> Are there builtins for maxNumMag and minNumMag? Or does anyone know what
> the “canonical” way to perform it is? I do not want to mess up corners
> cases, which is so easy to do…
TS 18661-1 defined functions fmaxmag and fminmag for those; we don't have
built-in functions for them, and C2x does not include those functions
given that those operations were also removed in IEEE 754-2019.
--
Joseph S. Myers
joseph@codesourcery.com
prev parent reply other threads:[~2022-09-01 19:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 8:04 FX
2022-09-01 8:19 ` Jakub Jelinek
2022-09-01 9:04 ` FX
2022-09-01 9:23 ` Jakub Jelinek
2022-09-01 10:06 ` FX
2022-09-01 15:21 ` Joseph Myers
2022-09-01 15:57 ` Marc Glisse
2022-09-01 16:22 ` Joseph Myers
2022-09-01 16:24 ` FX
2022-09-01 16:44 ` Joseph Myers
2022-09-01 18:15 ` FX
2022-09-01 14:32 ` Segher Boessenkool
2022-09-01 15:19 ` Joseph Myers
2022-09-01 18:38 ` FX
2022-09-01 19:13 ` Joseph Myers
2022-09-01 18:47 ` FX
2022-09-01 19:16 ` Joseph Myers [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=alpine.DEB.2.22.394.2209011913500.550568@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=fortran@gcc.gnu.org \
--cc=fxcoudert@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.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.
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).