From: Kito Cheng <kito.cheng@gmail.com>
To: juzhe.zhong@rivai.ai
Cc: gcc-patches@gcc.gnu.org, palmer@dabbelt.com
Subject: Re: [PATCH] RISC-V: Remove redundant attributes
Date: Sat, 28 Jan 2023 11:35:01 +0800 [thread overview]
Message-ID: <CA+yXCZCPb0=YHBNomVsmVfjA-5LqsU8vCBa2eySAtmCLaHYTWQ@mail.gmail.com> (raw)
In-Reply-To: <20230127225714.261700-1-juzhe.zhong@rivai.ai>
[-- Attachment #1: Type: text/plain, Size: 1399 bytes --]
committed, thanks!
On Sat, Jan 28, 2023 at 6:58 AM <juzhe.zhong@rivai.ai> wrote:
> From: Ju-Zhe Zhong <juzhe.zhong@rivai.ai>
>
> ---
> gcc/config/riscv/vector.md | 20 --------------------
> 1 file changed, 20 deletions(-)
>
> diff --git a/gcc/config/riscv/vector.md b/gcc/config/riscv/vector.md
> index 8c60eb20d72..4319266974d 100644
> --- a/gcc/config/riscv/vector.md
> +++ b/gcc/config/riscv/vector.md
> @@ -208,26 +208,6 @@
> (const_int 4)]
> (const_int INVALID_ATTRIBUTE)))
>
> -;; The index of operand[] to get the tail policy op.
> -(define_attr "tail_policy_op_idx" ""
> - (cond [(eq_attr "type" "vlde,vste,vimov,vfmov,vlds")
> - (const_int 5)]
> - (const_int INVALID_ATTRIBUTE)))
> -
> -;; The index of operand[] to get the mask policy op.
> -(define_attr "mask_policy_op_idx" ""
> - (cond [(eq_attr "type" "vlde,vste,vlds")
> - (const_int 6)]
> - (const_int INVALID_ATTRIBUTE)))
> -
> -;; The index of operand[] to get the mask policy op.
> -(define_attr "avl_type_op_idx" ""
> - (cond [(eq_attr "type"
> "vlde,vlde,vste,vimov,vimov,vimov,vfmov,vlds,vlds")
> - (const_int 7)
> - (eq_attr "type" "vldm,vstm,vimov,vmalu,vmalu")
> - (const_int 5)]
> - (const_int INVALID_ATTRIBUTE)))
> -
> ;; The tail policy op value.
> (define_attr "ta" ""
> (cond [(eq_attr "type" "vlde,vimov,vfmov,vlds")
> --
> 2.36.3
>
>
prev parent reply other threads:[~2023-01-28 3:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 22:57 juzhe.zhong
2023-01-28 3:35 ` 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+yXCZCPb0=YHBNomVsmVfjA-5LqsU8vCBa2eySAtmCLaHYTWQ@mail.gmail.com' \
--to=kito.cheng@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=juzhe.zhong@rivai.ai \
--cc=palmer@dabbelt.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).