From: Kito Cheng <kito.cheng@gmail.com>
To: juzhe.zhong@rivai.ai
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] RISC-V: Remove TUPLE size macro define.
Date: Wed, 12 Oct 2022 21:02:53 +0800 [thread overview]
Message-ID: <CA+yXCZDed74ikH3yOBRVgYvWJPMJahrPZZYceTdReydLZYLVOg@mail.gmail.com> (raw)
In-Reply-To: <20221011062333.70907-1-juzhe.zhong@rivai.ai>
Committed, thanks!
On Tue, Oct 11, 2022 at 2:23 PM <juzhe.zhong@rivai.ai> wrote:
>
> From: Ju-Zhe Zhong <juzhe.zhong@rivai.ai>
>
> gcc/ChangeLog:
>
> * config/riscv/riscv-vector-builtins.h: Remove redundant macro.
>
> ---
> gcc/config/riscv/riscv-vector-builtins.h | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/gcc/config/riscv/riscv-vector-builtins.h b/gcc/config/riscv/riscv-vector-builtins.h
> index 7d4b807f33c..cd6dad62ad8 100644
> --- a/gcc/config/riscv/riscv-vector-builtins.h
> +++ b/gcc/config/riscv/riscv-vector-builtins.h
> @@ -23,9 +23,6 @@
>
> namespace riscv_vector {
>
> -/* This is for segment instructions. */
> -const unsigned int MAX_TUPLE_SIZE = 8;
> -
> /* Enumerates the RVV types, together called
> "vector types" for brevity. */
> enum vector_type_index
> --
> 2.36.1
>
prev parent reply other threads:[~2022-10-12 13:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 6:23 juzhe.zhong
2022-10-12 13:02 ` Kito Cheng [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=CA+yXCZDed74ikH3yOBRVgYvWJPMJahrPZZYceTdReydLZYLVOg@mail.gmail.com \
--to=kito.cheng@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=juzhe.zhong@rivai.ai \
/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).