public inbox for binutils-cvs@sourceware.org
 help / color / mirror / Atom feed
From: Philipp Tomsich <ptomsich@sourceware.org>
To: bfd-cvs@sourceware.org
Subject: [binutils-gdb] binutils: NEWS: announce new RISC-V extensions
Date: Fri, 30 Jun 2023 14:04:51 +0000 (GMT)	[thread overview]
Message-ID: <20230630140451.8CE28387093B@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=e507570754867e3b74c01b55386067c30651c776

commit e507570754867e3b74c01b55386067c30651c776
Author: Philipp Tomsich <philipp.tomsich@vrull.eu>
Date:   Fri Jun 30 16:02:11 2023 +0200

    binutils: NEWS: announce new RISC-V extensions
    
    We picked up support for a few new extensions over the last weeks
    (this may need further updating prior to the next release), list them
    in the NEWS file.
    
    binutils/ChangeLog:
    
            * binutils/NEWS: announce suuport for the new RISC-V
              extensions (Zicond, Zfa, XVentanaCondOps).
    
    Signed-off-by: Philipp Tomsich <philipp.tomsich@vrull.eu>

Diff:
---
 binutils/NEWS | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/binutils/NEWS b/binutils/NEWS
index 7084aadabda..2e8d51d2773 100644
--- a/binutils/NEWS
+++ b/binutils/NEWS
@@ -20,6 +20,13 @@
 * Add command-line option, --strip-section-headers, to objcopy and strip to
   remove ELF section header from ELF file.
 
+* The RISC-V port now supports the following new standard extensions:
+  - Zicond (conditional zero instructions)
+  - Zfa (additional floating-point instructions)
+
+* The RISC-V port now supports the following vendor-defined extensions:
+  - XVentanaCondOps
+
 Changes in 2.40:
 
 * Objdump has a new command line option --show-all-symbols which will make it

                 reply	other threads:[~2023-06-30 14:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20230630140451.8CE28387093B@sourceware.org \
    --to=ptomsich@sourceware.org \
    --cc=bfd-cvs@sourceware.org \
    /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).