From: Richard Sandiford <richard.sandiford@arm.com>
To: "Kewen.Lin" <linkw@linux.ibm.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Richard Biener <richard.guenther@gmail.com>
Subject: Re: [PATCH] Update document for VECTOR_MODES_WITH_PREFIX
Date: Mon, 06 Jun 2022 11:01:57 +0100 [thread overview]
Message-ID: <mpth74ykt4a.fsf@arm.com> (raw)
In-Reply-To: <7fc14cb5-2635-636c-f39b-9f67403b34cd@linux.ibm.com> (Kewen Lin's message of "Mon, 6 Jun 2022 14:23:33 +0800")
"Kewen.Lin" <linkw@linux.ibm.com> writes:
> Hi,
>
> r10-3912 updated the format of VECTOR_MODES_WITH_PREFIX by
> adding one more parameter ORDER, the related document is out
> of date. So update the document for ORDER.
>
> Is it ok for trunk?
>
> BR,
> Kewen
> -----
>
> gcc/ChangeLog:
>
> * machmode.def (VECTOR_MODES_WITH_PREFIX): Update document for
> parameter ORDER.
OK, thanks.
Richard
> ---
> gcc/machmode.def | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/gcc/machmode.def b/gcc/machmode.def
> index b62a5fbc683..d62563601fc 100644
> --- a/gcc/machmode.def
> +++ b/gcc/machmode.def
> @@ -142,9 +142,10 @@ along with GCC; see the file COPYING3. If not see
> than two bytes (if CLASS is FLOAT). CLASS must be INT or
> FLOAT. The names follow the same rule as VECTOR_MODE uses.
>
> - VECTOR_MODES_WITH_PREFIX (PREFIX, CLASS, WIDTH);
> + VECTOR_MODES_WITH_PREFIX (PREFIX, CLASS, WIDTH, ORDER);
> Like VECTOR_MODES, but start the mode names with PREFIX instead
> - of the usual "V".
> + of the usual "V". ORDER is the top-level sorting order of the
> + mode, with smaller numbers indicating a higher priority.
>
> VECTOR_BOOL_MODE (NAME, COUNT, COMPONENT, BYTESIZE)
> Create a vector mode called NAME that contains COUNT boolean
> --
> 2.27.0
next prev parent reply other threads:[~2022-06-06 10:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 6:23 Kewen.Lin
2022-06-06 10:01 ` Richard Sandiford [this message]
2022-06-07 3:11 ` 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=mpth74ykt4a.fsf@arm.com \
--to=richard.sandiford@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=linkw@linux.ibm.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).