public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <richard.guenther@gmail.com>
To: liuhongt <hongtao.liu@intel.com>
Cc: gcc-patches@gcc.gnu.org, crazylht@gmail.com
Subject: Re: [PATCH] Document signbitm2.
Date: Fri, 31 Mar 2023 10:51:58 +0200	[thread overview]
Message-ID: <CAFiYyc0sCzjWWFfTNQy_xXCKoF9qbinUbMwxjP-ByiRi5EgUnQ@mail.gmail.com> (raw)
In-Reply-To: <20230331065810.4012545-1-hongtao.liu@intel.com>

On Fri, Mar 31, 2023 at 8:59 AM liuhongt via Gcc-patches
<gcc-patches@gcc.gnu.org> wrote:
>
> Look through all backends which defined signbitm2.
> 1. When m is a scalar mode, the dest is SImode.
> 2. When m is a vector mode, the dest mode is the vector integer
> mode has the same size and elements number as m.
>
> Ok for trunk?

OK.

> gcc/ChangeLog:
>
>         * doc/md.texi: Document signbitm2.
> ---
>  gcc/doc/md.texi | 11 +++++++++++
>  1 file changed, 11 insertions(+)
>
> diff --git a/gcc/doc/md.texi b/gcc/doc/md.texi
> index 8e3113599fd..edfa51e867a 100644
> --- a/gcc/doc/md.texi
> +++ b/gcc/doc/md.texi
> @@ -6030,6 +6030,17 @@ floating-point mode.
>
>  This pattern is not allowed to @code{FAIL}.
>
> +@cindex @code{signbit@var{m}2} instruction pattern
> +@item @samp{signbit@var{m}2}
> +Store the sign bit of floating-point operand 1 in operand 0.
> +@var{m} is either a scalar or vector mode.  When it is a scalar,
> +operand 1 has mode @var{m} but operand 0 must have mode @code{SImode}.
> +When @var{m} is a vector, operand 1 has the mode @var{m}.
> +operand 0's mode should be an vector integer mode which has
> +the same number of elements and the same size as mode @var{m}.
> +
> +This pattern is not allowed to @code{FAIL}.
> +
>  @cindex @code{significand@var{m}2} instruction pattern
>  @item @samp{significand@var{m}2}
>  Store the significand of floating-point operand 1 in operand 0.
> --
> 2.39.1.388.g2fc9e9ca3c
>

      reply	other threads:[~2023-03-31  8:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-31  6:58 liuhongt
2023-03-31  8:51 ` 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=CAFiYyc0sCzjWWFfTNQy_xXCKoF9qbinUbMwxjP-ByiRi5EgUnQ@mail.gmail.com \
    --to=richard.guenther@gmail.com \
    --cc=crazylht@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hongtao.liu@intel.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).