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>,
	Nelson Chu <nelson@rivosinc.com>,
	Kito Cheng <kito.cheng@sifive.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Andrew Waterman <andrew@sifive.com>
Cc: binutils@sourceware.org
Subject: [RFC PATCH 0/1] RISC-V: Imply 'Zicsr' from privileged extensions with CSRs
Date: Sat,  8 Oct 2022 04:32:17 +0000	[thread overview]
Message-ID: <cover.1665203531.git.research_trasio@irq.a4lg.com> (raw)

Hello,

'H', 'Smstateen', 'Sscofpmf' and 'Sstc' are four privileged extensions with
their CSR definitions and 'Smepmp' is a privileged extension with additional
CSR bits.

Volume II: Privileged Architecture of the RISC-V ISA Manual states that the
privileged architecture requires the 'Zicsr' extension.  However, current
GNU Binutils has no direct way whether the program has dependency to the
privileged architecture itself.

As a workaround, we could add implications from privileged extensions that
either add new CSRs, extend existing CSRs or depends on using CSRs.

This patchset adds such implications for existing privileged extensions that
satisfy this condition.

I would like to hear your thoughts.


Thanks,
Tsukasa




Tsukasa OI (1):
  RISC-V: Imply 'Zicsr' from privileged extensions with CSRs

 bfd/elfxx-riscv.c                       | 5 +++++
 gas/testsuite/gas/riscv/march-imply-h.d | 6 ++++++
 2 files changed, 11 insertions(+)
 create mode 100644 gas/testsuite/gas/riscv/march-imply-h.d


base-commit: 4cbfd0daabd68516651ee37a19d0e24ca4789ea3
-- 
2.34.1


             reply	other threads:[~2022-10-08  4:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-08  4:32 Tsukasa OI [this message]
2022-10-08  4:32 ` [RFC PATCH 1/1] " Tsukasa OI
2022-10-14  2:17 ` [RFC PATCH 0/1] " 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.1665203531.git.research_trasio@irq.a4lg.com \
    --to=research_trasio@irq.a4lg.com \
    --cc=andrew@sifive.com \
    --cc=binutils@sourceware.org \
    --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).