From: Richard Biener <richard.guenther@gmail.com>
To: Richard Sandiford <richard.sandiford@arm.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] doc: Document cond_* shift optabs in md.texi
Date: Thu, 5 Aug 2021 12:48:11 +0200 [thread overview]
Message-ID: <CAFiYyc2gEsfEhKecWAK_+nZLUp=J3j5hG8v0Fa2A5AaSQ9g1Vw@mail.gmail.com> (raw)
In-Reply-To: <mptzgtw41qc.fsf@arm.com>
On Thu, Aug 5, 2021 at 12:37 PM Richard Sandiford via Gcc-patches
<gcc-patches@gcc.gnu.org> wrote:
>
> As per $SUBJECT. OK to install?
OK.
> Richard
>
>
> gcc/
> PR middle-end/101787
> * doc/md.texi (cond_ashl, cond_ashr, cond_lshr): Document.
> ---
> gcc/doc/md.texi | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/gcc/doc/md.texi b/gcc/doc/md.texi
> index f6d1bc1ad0f..f8047aefccc 100644
> --- a/gcc/doc/md.texi
> +++ b/gcc/doc/md.texi
> @@ -6921,6 +6921,9 @@ operand 0, otherwise (operand 2 + operand 3) is moved.
> @cindex @code{cond_smax@var{mode}} instruction pattern
> @cindex @code{cond_umin@var{mode}} instruction pattern
> @cindex @code{cond_umax@var{mode}} instruction pattern
> +@cindex @code{cond_ashl@var{mode}} instruction pattern
> +@cindex @code{cond_ashr@var{mode}} instruction pattern
> +@cindex @code{cond_lshr@var{mode}} instruction pattern
> @item @samp{cond_add@var{mode}}
> @itemx @samp{cond_sub@var{mode}}
> @itemx @samp{cond_mul@var{mode}}
> @@ -6935,6 +6938,9 @@ operand 0, otherwise (operand 2 + operand 3) is moved.
> @itemx @samp{cond_smax@var{mode}}
> @itemx @samp{cond_umin@var{mode}}
> @itemx @samp{cond_umax@var{mode}}
> +@itemx @samp{cond_ashl@var{mode}}
> +@itemx @samp{cond_ashr@var{mode}}
> +@itemx @samp{cond_lshr@var{mode}}
> When operand 1 is true, perform an operation on operands 2 and 3 and
> store the result in operand 0, otherwise store operand 4 in operand 0.
> The operation works elementwise if the operands are vectors.
> @@ -6962,6 +6968,11 @@ Operands 0, 2, 3 and 4 all have mode @var{m}. Operand 1 is a scalar
> integer if @var{m} is scalar, otherwise it has the mode returned by
> @code{TARGET_VECTORIZE_GET_MASK_MODE}.
>
> +@samp{cond_@var{op}@var{mode}} generally corresponds to a conditional
> +form of @samp{@var{op}@var{mode}3}. As an exception, the vector forms
> +of shifts correspond to patterns like @code{vashl@var{mode}3} rather
> +than patterns like @code{ashl@var{mode}3}.
> +
> @cindex @code{cond_fma@var{mode}} instruction pattern
> @cindex @code{cond_fms@var{mode}} instruction pattern
> @cindex @code{cond_fnma@var{mode}} instruction pattern
> --
> 2.17.1
>
prev parent reply other threads:[~2021-08-05 10:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-05 10:36 Richard Sandiford
2021-08-05 10:48 ` Richard Biener [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='CAFiYyc2gEsfEhKecWAK_+nZLUp=J3j5hG8v0Fa2A5AaSQ9g1Vw@mail.gmail.com' \
--to=richard.guenther@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.sandiford@arm.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).