public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Jeff Law <jeffreyalaw@gmail.com>
To: Christoph Muellner <christoph.muellner@vrull.eu>,
	binutils@sourceware.org, Nelson Chu <nelson@rivosinc.com>,
	Andrew Waterman <andrew@sifive.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Jim Wilson <jim.wilson.gcc@gmail.com>,
	Philipp Tomsich <philipp.tomsich@vrull.eu>,
	Aaron Durbin <adurbin@rivosinc.com>,
	Andrew de los Reyes <adlr@rivosinc.com>,
	Eric Gouriou <ego@rivosinc.com>,
	Barna Ibrahim <barna@rivosinc.com>
Subject: Re: [RFC PATCH 3/6] RISC-V: Add Zvkh[a,b] ISA extension support
Date: Wed, 21 Dec 2022 14:24:15 -0700	[thread overview]
Message-ID: <be46ac8d-bfdb-91c7-3044-15a26d40aa97@gmail.com> (raw)
In-Reply-To: <20221221170706.2877188-4-christoph.muellner@vrull.eu>



On 12/21/22 10:07, Christoph Muellner wrote:
> From: Christoph Müllner <christoph.muellner@vrull.eu>
> 
> This commit adds the Zvkh[a,b] ISA extension instructions, which are part
> of the vector crypto extensions.
> 
> Signed-off-by: Christoph Müllner <christoph.muellner@vrull.eu>
> ---
>   bfd/elfxx-riscv.c                     | 13 +++++++++++++
>   gas/testsuite/gas/riscv/zvkha.d       | 12 ++++++++++++
>   gas/testsuite/gas/riscv/zvkha_zvkhb.s |  3 +++
>   gas/testsuite/gas/riscv/zvkhb.d       | 12 ++++++++++++
>   include/opcode/riscv-opc.h            | 11 +++++++++++
>   include/opcode/riscv.h                |  3 +++
>   opcodes/riscv-opc.c                   |  5 +++++
>   7 files changed, 59 insertions(+)
>   create mode 100644 gas/testsuite/gas/riscv/zvkha.d
>   create mode 100644 gas/testsuite/gas/riscv/zvkha_zvkhb.s
>   create mode 100644 gas/testsuite/gas/riscv/zvkhb.d
Looks reasonable to me.  Just one comment nit below...



> diff --git a/opcodes/riscv-opc.c b/opcodes/riscv-opc.c
> index bb716c8c9d0..35d3e653147 100644
> --- a/opcodes/riscv-opc.c
> +++ b/opcodes/riscv-opc.c
> @@ -1834,6 +1834,11 @@ const struct riscv_opcode riscv_opcodes[] =
>   /* Zvkg instructions.  */
>   {"vghmac.vv",   0, INSN_CLASS_ZVKG, "Vd,Vt,Vs", MATCH_VGHMACVV, MASK_VGHMACVV, match_opcode, 0},
>   
> +/* Xvkh[a,b] instructions.  */
Are these X or Z?

Jeff

  reply	other threads:[~2022-12-21 21:24 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-21 17:07 [RFC PATCH 0/6] RISC-V: Add support for vector crypto extensions Christoph Muellner
2022-12-21 17:07 ` [RFC PATCH 1/6] RISC-V: Add Zvkb ISA extension support Christoph Muellner
2022-12-21 20:50   ` Jeff Law
2022-12-22 14:23     ` Christoph Müllner
2023-01-20 19:04   ` Philipp Tomsich
2023-01-20 19:21     ` Christoph Müllner
2022-12-21 17:07 ` [RFC PATCH 2/6] RISC-V: Add Zvkg " Christoph Muellner
2022-12-21 21:16   ` Jeff Law
2022-12-21 17:07 ` [RFC PATCH 3/6] RISC-V: Add Zvkh[a,b] " Christoph Muellner
2022-12-21 21:24   ` Jeff Law [this message]
2022-12-22 14:17     ` Christoph Müllner
2023-01-03 22:00   ` Philipp Tomsich
2022-12-21 17:07 ` [RFC PATCH 4/6] RISC-V: Add Zvkn " Christoph Muellner
2022-12-21 21:26   ` Jeff Law
2022-12-21 17:07 ` [RFC PATCH 5/6] RISC-V: Add Zvksed " Christoph Muellner
2022-12-21 21:30   ` Jeff Law
2022-12-21 17:07 ` [RFC PATCH 6/6] RISC-V: Add Zvksh " Christoph Muellner
2022-12-21 21:33   ` Jeff Law
2022-12-22  2:46 ` [RFC PATCH 0/6] RISC-V: Add support for vector crypto extensions Kito Cheng

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=be46ac8d-bfdb-91c7-3044-15a26d40aa97@gmail.com \
    --to=jeffreyalaw@gmail.com \
    --cc=adlr@rivosinc.com \
    --cc=adurbin@rivosinc.com \
    --cc=andrew@sifive.com \
    --cc=barna@rivosinc.com \
    --cc=binutils@sourceware.org \
    --cc=christoph.muellner@vrull.eu \
    --cc=ego@rivosinc.com \
    --cc=jim.wilson.gcc@gmail.com \
    --cc=nelson@rivosinc.com \
    --cc=palmer@dabbelt.com \
    --cc=philipp.tomsich@vrull.eu \
    /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).