From: Christoph Muellner <christoph.muellner@vrull.eu>
To: binutils@sourceware.org, Nathan Huckleberry <nhuck@google.com>,
nhuck@pmull.org, Jeff Law <jeffreyalaw@gmail.com>,
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>
Cc: "Christoph Müllner" <christoph.muellner@vrull.eu>
Subject: [PATCH v5 15/15] binutils: NEWS: Announce new RISC-V vector crypto extensions
Date: Fri, 30 Jun 2023 23:57:25 +0200 [thread overview]
Message-ID: <20230630215725.3725876-16-christoph.muellner@vrull.eu> (raw)
In-Reply-To: <20230630215725.3725876-1-christoph.muellner@vrull.eu>
From: Christoph Müllner <christoph.muellner@vrull.eu>
This commit adds the recently added support of the RISC-V vector crypto
extensions to the NEWS file.
binutils/ChangeLog:
* NEWS: Announce new RISC-V vector crypto extensions.
Signed-off-by: Christoph Müllner <christoph.muellner@vrull.eu>
---
binutils/NEWS | 2 ++
1 file changed, 2 insertions(+)
diff --git a/binutils/NEWS b/binutils/NEWS
index 2e8d51d2773..834e648db6c 100644
--- a/binutils/NEWS
+++ b/binutils/NEWS
@@ -23,6 +23,8 @@
* The RISC-V port now supports the following new standard extensions:
- Zicond (conditional zero instructions)
- Zfa (additional floating-point instructions)
+ - Zvbb, Zvbc, Zvkg, Zvkned, Zvknh[ab], Zvksed, Zvksh, Zvkn, Zvknc, Zvkng,
+ Zvks, Zvksc, Zvkg, Zvkt (vector crypto instructions)
* The RISC-V port now supports the following vendor-defined extensions:
- XVentanaCondOps
--
2.41.0
prev parent reply other threads:[~2023-06-30 21:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-30 21:57 [PATCH v5 00/15] RISC-V: Add support for " Christoph Muellner
2023-06-30 21:57 ` [PATCH v5 01/15] RISC-V: Add support for the Zvbb ISA extension Christoph Muellner
2023-06-30 21:57 ` [PATCH v5 02/15] RISC-V: Add support for the Zvbc extension Christoph Muellner
2023-06-30 21:57 ` [PATCH v5 03/15] RISC-V: Add support for the Zvkg ISA extension Christoph Muellner
2023-06-30 21:57 ` [PATCH v5 04/15] RISC-V: Add support for the Zvkned " Christoph Muellner
2023-06-30 21:57 ` [PATCH v5 05/15] RISC-V: Add support for the Zvknh[a,b] ISA extensions Christoph Muellner
2023-06-30 21:57 ` [PATCH v5 06/15] RISC-V: Add support for the Zvksed ISA extension Christoph Muellner
2023-06-30 21:57 ` [PATCH v5 07/15] RISC-V: Add support for the Zvksh " Christoph Muellner
2023-06-30 21:57 ` [PATCH v5 08/15] RISC-V: Add support for the Zvkn " Christoph Muellner
2023-06-30 21:57 ` [PATCH v5 09/15] RISC-V: Allow nested implications for extensions Christoph Muellner
2023-06-30 21:57 ` [PATCH v5 10/15] RISC-V: Add support for the Zvkng ISA extension Christoph Muellner
2023-06-30 21:57 ` [PATCH v5 11/15] RISC-V: Add support for the Zvks " Christoph Muellner
2023-06-30 21:57 ` [PATCH v5 12/15] RISC-V: Add support for the Zvksg " Christoph Muellner
2023-06-30 21:57 ` [PATCH v5 13/15] RISC-V: Add support for the Zvknc " Christoph Muellner
2023-06-30 21:57 ` [PATCH v5 14/15] RISC-V: Add support for the Zvksc " Christoph Muellner
2023-06-30 21:57 ` Christoph Muellner [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=20230630215725.3725876-16-christoph.muellner@vrull.eu \
--to=christoph.muellner@vrull.eu \
--cc=andrew@sifive.com \
--cc=binutils@sourceware.org \
--cc=jeffreyalaw@gmail.com \
--cc=jim.wilson.gcc@gmail.com \
--cc=nelson@rivosinc.com \
--cc=nhuck@google.com \
--cc=nhuck@pmull.org \
--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).