public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Kito Cheng <kito.cheng@sifive.com>
To: Jiawei <jiawei@iscas.ac.cn>
Cc: binutils@sourceware.org, nelson@rivosinc.com, palmer@dabbelt.com,
	 jbeulich@suse.com, christoph.muellner@vrull.eu,
	wuwei2016@iscas.ac.cn,  shihua@iscas.ac.cn,
	shiyulong@iscas.ac.cn, chenyixuan@iscas.ac.cn
Subject: Re: [PATCH] RISC-V: Remove redundant RVV opcode definitions
Date: Tue, 25 Jul 2023 21:27:17 +0800	[thread overview]
Message-ID: <CALLt3Tj3VpY7cSgmax4EtjPqPQV1OX4GWaLc9OTJXDATxaG+Kw@mail.gmail.com> (raw)
In-Reply-To: <20230725104738.8619-1-jiawei@iscas.ac.cn>

Reviewed-by: Kito Cheng <kito.cheng@sifive.com>

On Tue, Jul 25, 2023 at 6:47 PM Jiawei <jiawei@iscas.ac.cn> wrote:
>
> Remove redundant rvv opcodes that not use currently.
>
> include/ChangeLog:
>
>         * opcode/riscv-opc.h (MATCH_VDOTVV): Deleted.
>         (MASK_VDOTVV): Ditto.
>         (MATCH_VDOTUVV): Ditto.
>         (MASK_VDOTUVV): Ditto.
>         (MATCH_VFDOTVV): Ditto.
>         (MASK_VFDOTVV): Ditto.
>
> ---
>  include/opcode/riscv-opc.h | 6 ------
>  1 file changed, 6 deletions(-)
>
> diff --git a/include/opcode/riscv-opc.h b/include/opcode/riscv-opc.h
> index 53f5f200508..e3ffc9092c9 100644
> --- a/include/opcode/riscv-opc.h
> +++ b/include/opcode/riscv-opc.h
> @@ -2115,12 +2115,6 @@
>  #define MASK_VMV4RV  0xfe0ff07f
>  #define MATCH_VMV8RV  0x9e03b057
>  #define MASK_VMV8RV  0xfe0ff07f
> -#define MATCH_VDOTVV  0xe4000057
> -#define MASK_VDOTVV  0xfc00707f
> -#define MATCH_VDOTUVV  0xe0000057
> -#define MASK_VDOTUVV  0xfc00707f
> -#define MATCH_VFDOTVV  0xe4001057
> -#define MASK_VFDOTVV  0xfc00707f
>  /* Zvbb instructions.  */
>  #define MATCH_VANDN_VV 0x4000057
>  #define MASK_VANDN_VV 0xfc00707f
> --
> 2.25.1
>

      reply	other threads:[~2023-07-25 13:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-25 10:47 Jiawei
2023-07-25 13:27 ` 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=CALLt3Tj3VpY7cSgmax4EtjPqPQV1OX4GWaLc9OTJXDATxaG+Kw@mail.gmail.com \
    --to=kito.cheng@sifive.com \
    --cc=binutils@sourceware.org \
    --cc=chenyixuan@iscas.ac.cn \
    --cc=christoph.muellner@vrull.eu \
    --cc=jbeulich@suse.com \
    --cc=jiawei@iscas.ac.cn \
    --cc=nelson@rivosinc.com \
    --cc=palmer@dabbelt.com \
    --cc=shihua@iscas.ac.cn \
    --cc=shiyulong@iscas.ac.cn \
    --cc=wuwei2016@iscas.ac.cn \
    /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).