From: Segher Boessenkool <segher@kernel.crashing.org>
To: HAO CHEN GUI <guihaoc@linux.ibm.com>
Cc: "Kewen.Lin" <linkw@linux.ibm.com>,
gcc-patches <gcc-patches@gcc.gnu.org>, David <dje.gcc@gmail.com>,
Peter Bergner <bergner@linux.ibm.com>
Subject: Re: [PATCH v6, rs6000] Implemented f[min/max]_optab by xs[min/max]dp [PR103605]
Date: Thu, 22 Sep 2022 08:56:42 -0500 [thread overview]
Message-ID: <20220922135642.GH25951@gate.crashing.org> (raw)
In-Reply-To: <fe24d049-a800-9835-486c-0a6bd7280f43@linux.ibm.com>
Hi!
On Thu, Sep 22, 2022 at 05:59:07PM +0800, HAO CHEN GUI wrote:
> >> I still think we should get RTL codes for this, to have access to proper
> >> floating point min/max semantics always and everywhere. "fmin" and
> >> "fmax" seem to be good names :-)
> >
> > It would be good, especially if we have observed some uses of these bifs
> > and further opportunities around them. :)
> >
> Shall we submit a PR to add fmin/fmax to RTL codes?
Yes, please do.
If we have fmin/fmax RTL codes that describe the standard semantics,
we can generate code for that with -ffast-math as well, since the
code generated is optimal in either case; it's just the *generic*
optimisations that fall behind.
Segher
next prev parent reply other threads:[~2022-09-22 13:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 2:02 HAO CHEN GUI
2022-07-04 6:32 ` Ping " HAO CHEN GUI
2022-08-01 2:03 ` Ping^2 " HAO CHEN GUI
2022-09-21 5:20 ` Ping^3 " HAO CHEN GUI
2022-09-21 9:34 ` Kewen.Lin
2022-09-21 21:56 ` Segher Boessenkool
2022-09-22 2:28 ` Kewen.Lin
2022-09-22 9:59 ` HAO CHEN GUI
2022-09-22 13:56 ` Segher Boessenkool [this message]
2022-09-22 14:05 ` Segher Boessenkool
2022-09-26 5:58 ` Kewen.Lin
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=20220922135642.GH25951@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=bergner@linux.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=guihaoc@linux.ibm.com \
--cc=linkw@linux.ibm.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).