From: Segher Boessenkool <segher@kernel.crashing.org>
To: HAO CHEN GUI <guihaoc@linux.ibm.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>, David <dje.gcc@gmail.com>,
"Kewen.Lin" <linkw@linux.ibm.com>,
Peter Bergner <bergner@linux.ibm.com>,
Andrew Pinski <pinskia@gmail.com>,
Richard Biener <richard.guenther@gmail.com>
Subject: Re: [PATCHv3] Optab: add isfinite_optab for __builtin_isfinite
Date: Tue, 28 May 2024 17:19:56 -0500 [thread overview]
Message-ID: <20240528221956.GW19790@gate.crashing.org> (raw)
In-Reply-To: <936073f2-dfd4-4650-9b28-b905d97be477@linux.ibm.com>
Hi!
On Mon, May 27, 2024 at 05:37:23PM +0800, HAO CHEN GUI wrote:
> --- a/gcc/builtins.cc
> +++ b/gcc/builtins.cc
> @@ -2459,8 +2459,9 @@ interclass_mathfn_icode (tree arg, tree fndecl)
> errno_set = true; builtin_optab = ilogb_optab; break;
> CASE_FLT_FN (BUILT_IN_ISINF):
> builtin_optab = isinf_optab; break;
> - case BUILT_IN_ISNORMAL:
> case BUILT_IN_ISFINITE:
> + builtin_optab = isfinite_optab; break;
This needs a line break after the first ; (like after *any* semicolon
in C). It is rather important that every "break;" stands out :-)
> +@cindex @code{isfinite@var{m}2} instruction pattern
> +@item @samp{isfinite@var{m}2}
> +Set operand 0 to nonzero if operand 1 is a finite @code{SFmode},
> +@code{DFmode}, or @code{TFmode} floating point number and to 0
> +otherwise.
operand 0 is the output of the builtin, right? So write that instead?
"Return 1 if the operand (a scalar floating poiint number) is finite",
or such?
Segher
prev parent reply other threads:[~2024-05-28 22:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 9:37 HAO CHEN GUI
2024-05-27 12:54 ` Richard Biener
2024-05-28 7:09 ` Kewen.Lin
2024-05-28 12:09 ` Richard Biener
2024-05-28 22:09 ` Segher Boessenkool
2024-05-29 1:57 ` Kewen.Lin
2024-05-28 21:46 ` Richard Sandiford
2024-05-28 22:19 ` Segher Boessenkool [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=20240528221956.GW19790@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 \
--cc=pinskia@gmail.com \
--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).