public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Tsukasa OI <research_trasio@irq.a4lg.com>
To: Tsukasa OI <research_trasio@irq.a4lg.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Andrew Waterman <andrew@sifive.com>,
	Jim Wilson <jim.wilson.gcc@gmail.com>,
	Nelson Chu <nelson@rivosinc.com>,
	Kito Cheng <kito.cheng@sifive.com>
Cc: binutils@sourceware.org
Subject: [REVIEW ONLY 0/1] RISC-V: Add stub support for the 'Svadu' extension
Date: Sun,  3 Sep 2023 03:13:23 +0000	[thread overview]
Message-ID: <cover.1693710769.git.research_trasio@irq.a4lg.com> (raw)
In-Reply-To: <cover.1669684692.git.research_trasio@irq.a4lg.com>

Hi,

This is non-review-only patch set for the 'Svadu' extension.
REVIEW ONLY (2022-11-29):
<https://sourceware.org/pipermail/binutils/2022-November/124752.html>

Because this extension is now frozen, unlikely to change and adds no new
instructions or CSRs (but a new bit to an existing CSR), this patch set
only adds extension name / implication support.

This patch set is based on the version 1.0-rc1 (Frozen):
<https://github.com/riscv/riscv-svadu/releases/tag/v1.0-rc1>

Thanks,
Tsukasa




Tsukasa OI (1):
  RISC-V: Add stub support for the 'Svadu' extension

 bfd/elfxx-riscv.c | 2 ++
 1 file changed, 2 insertions(+)


base-commit: a496e1a71e1766d4bb02b241cb23e2e9874d2605
-- 
2.42.0


  parent reply	other threads:[~2023-09-03  3:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-29  1:18 [REVIEW ONLY 0/1] UNRATIFIED RISC-V: Add " Tsukasa OI
2022-11-29  1:18 ` [REVIEW ONLY 1/1] " Tsukasa OI
2022-11-29  1:57   ` Palmer Dabbelt
2023-09-03  3:13 ` Tsukasa OI [this message]
2023-09-03  3:13   ` [REVIEW ONLY 1/1] RISC-V: Add stub support for the " Tsukasa OI
2023-09-03  3:16   ` [REVIEW ONLY 0/1] " Tsukasa OI
2023-09-05  6:55     ` Nelson Chu

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=cover.1693710769.git.research_trasio@irq.a4lg.com \
    --to=research_trasio@irq.a4lg.com \
    --cc=andrew@sifive.com \
    --cc=binutils@sourceware.org \
    --cc=jim.wilson.gcc@gmail.com \
    --cc=kito.cheng@sifive.com \
    --cc=nelson@rivosinc.com \
    --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).