From: Joseph Myers <joseph@codesourcery.com>
To: Janne Blomqvist <blomqvist.janne@gmail.com>
Cc: "Thomas König" <tk@tkoenig.net>,
"Kyrill Tkachov" <kyrylo.tkachov@foss.arm.com>,
"Thomas Koenig" <tkoenig@netcologne.de>,
"Richard Biener" <richard.guenther@gmail.com>,
"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
"GCC Patches" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH][Fortran][v2] Use MIN/MAX_EXPR for min/max intrinsics
Date: Thu, 26 Jul 2018 20:36:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1807262031300.6526@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CAO9iq9G7rSWCFMkTam2uOAsuW9WBGJL607C4FtAeXqVh7th-Pw@mail.gmail.com>
On Wed, 18 Jul 2018, Janne Blomqvist wrote:
> minimumNumber(a, NaN) = minimumNumber(NaN, a) = a
>
> That is minimumNumber corresponds to minnum in IEEE 754-2008 and fmin* in
No, it differs in the handling of signaling NaNs (with minimumNumber, if
the NaN argument is signaling, it results in the "invalid" exception but
the non-NaN argument is still returned, whereas with minNum, a quiet NaN
was returned in that case). A new fminimum_num function is proposed as a
C binding to the new operation.
http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2273.pdf
(The new operations are also more strictly defined regarding zero
arguments, to treat -0 as less than +0, which was unspecified for minNum
and fmin.)
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2018-07-26 20:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-17 12:35 [PATCH][Fortran] Use MIN/MAX_EXPR for intrinsics or __builtin_fmin/max when appropriate Kyrill Tkachov
2018-07-17 13:27 ` Richard Biener
2018-07-17 13:46 ` Kyrill Tkachov
2018-07-17 15:37 ` Thomas Koenig
2018-07-17 16:16 ` Kyrill Tkachov
2018-07-17 17:42 ` Thomas Koenig
2018-07-17 20:06 ` Janne Blomqvist
2018-07-17 20:35 ` Janne Blomqvist
2018-07-18 11:17 ` [PATCH][Fortran][v2] Use MIN/MAX_EXPR for min/max intrinsics Kyrill Tkachov
2018-07-18 13:26 ` Thomas König
2018-07-18 14:03 ` Kyrill Tkachov
2018-07-18 14:55 ` Janne Blomqvist
2018-07-18 15:28 ` Richard Sandiford
2018-07-18 16:04 ` Kyrill Tkachov
2018-07-18 15:10 ` Janne Blomqvist
2018-07-26 20:36 ` Joseph Myers [this message]
2018-08-06 12:05 ` Janne Blomqvist
2018-07-18 9:44 ` [PATCH][Fortran] Use MIN/MAX_EXPR for intrinsics or __builtin_fmin/max when appropriate Richard Biener
2018-07-18 9:50 ` Kyrill Tkachov
2018-07-18 10:06 ` Richard Biener
2018-07-18 11:45 ` [PATCH]Use " Richard Sandiford
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.20.1807262031300.6526@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=blomqvist.janne@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=kyrylo.tkachov@foss.arm.com \
--cc=richard.guenther@gmail.com \
--cc=tk@tkoenig.net \
--cc=tkoenig@netcologne.de \
/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).