From: Joseph Myers <joseph@codesourcery.com>
To: Richard Biener <richard.guenther@gmail.com>
Cc: David Sherwood <david.sherwood@arm.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Richard Sandiford <Richard.Sandiford@arm.com>
Subject: Re: [PING][Patch] Add support for IEEE-conformant versions of scalar fmin* and fmax*
Date: Mon, 14 Sep 2015 20:38:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.10.1509142020230.22006@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CAFiYyc0SaX=UEjmF_C67Ogn33vgO5bSN9pHpnfRwQjkYEOztsw@mail.gmail.com>
On Mon, 14 Sep 2015, Richard Biener wrote:
> To make progess here I think adding new optabs is fine. So can you
> split out that part and implement builtin expanders
> for fmin/max instead?
>
> Btw, FMIN/MAX_EXPR are not commutative AFAIK because of behavior for
> fmax (-NaN, NaN)
> vs. fmax (NaN, -NaN)?
For those cases, it's unspecified which NaN is returned, so they can be
considered commutative (and likewise for the case when the arguments are 0
and -0).
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2015-09-14 20:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-13 10:13 David Sherwood
2015-08-13 11:12 ` Richard Biener
2015-08-17 9:41 ` David Sherwood
2015-08-17 14:02 ` Richard Biener
2015-08-18 11:10 ` David Sherwood
2015-08-18 13:31 ` Richard Biener
2015-08-18 14:20 ` Richard Sandiford
2015-08-19 9:48 ` Richard Biener
2015-08-19 10:04 ` Richard Sandiford
2015-08-19 10:31 ` Richard Biener
2015-08-19 12:23 ` Richard Sandiford
2015-08-19 12:35 ` Richard Biener
2015-08-19 13:16 ` Richard Sandiford
2015-08-19 13:41 ` Richard Biener
2015-09-14 10:47 ` David Sherwood
2015-09-14 13:42 ` Richard Biener
2015-09-14 20:38 ` Joseph Myers [this message]
2015-08-19 15:32 ` Joseph Myers
2015-11-23 9:21 ` David Sherwood
2015-11-25 12:39 ` Richard Biener
2015-08-19 15:07 ` Michael Matz
2015-08-19 15:25 ` Richard Biener
2015-08-19 15:39 ` Richard Sandiford
-- strict thread matches above, loose matches on Subject: below --
2015-08-06 9:39 David Sherwood
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.10.1509142020230.22006@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=Richard.Sandiford@arm.com \
--cc=david.sherwood@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.guenther@gmail.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).