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>
Cc: binutils@sourceware.org
Subject: [REVIEW ONLY v2 0/1] UNRATIFIED RISC-V: Add support for Core-Local Interrupt Controller (CLIC) extensions and their CSRs
Date: Tue, 12 Sep 2023 01:39:07 +0000	[thread overview]
Message-ID: <cover.1694482743.git.research_trasio@irq.a4lg.com> (raw)
In-Reply-To: <cover.1669684774.git.research_trasio@irq.a4lg.com>

*** WAIT FOR SPECIFICATION FREEZE ***
This is an implementation for unratified and not frozen RISC-V extension
and not intended to be merged for now.
The only intent to submit this patchset is to test new instructions for
your (possibly virtual) environment and early review for fast adoption
after ratification.

It's long since I submitted the previous version and it's a good time to
submit new REVIEW ONLY one, knowing if it's unratified.


Changes: v1 -> v2
*   Rebased against the latest master.
*   Added support for 'Smclicconfig', 'Smclicshv' and 'Ssclic' extensions
    (following the latest CLIC specification).
*   Added diagnostics-only support for the 'Suclic' extension (likewise).


This patchset adds following unratified extensions to GNU Binutils from the
Core-Local Interrupt Controller (CLIC) RISC-V Privileged Architecture
Extensions:

1.  'Smclic'
2.  'Smclicconfig'
3.  'Smclicshv'
4.  'Ssclic'
5.  'Suclic'
    (because 'N' extension support is now dropped by GNU Binutils,
     this extension is only supported to generate correct diagnostics
     that's why this extension is *not* in riscv_supported_std_s_ext).

that add 18 CSRs in total.

These extensions are software side of Core-Local Interrupt Controller (CLIC)
which provides lower latency local interrupts.


This is based on the specification document, version 0.9-draft:
<https://github.com/riscv/riscv-fast-interrupt/blob/894a16ce89dcf2c084dd951866448c2e756d3efa/clic.pdf>


Although that 18 CSRs are assigned with actual numbers (this is why I'm not
attaching "CSR instantiation" script in this patchset), it may be changed
before ratification.  Be careful.

Thanks,
Tsukasa




Tsukasa OI (1):
  UNRATIFIED RISC-V: Add CLIC extensions with CSRs

 bfd/elfxx-riscv.c                           | 10 ++-
 gas/config/tc-riscv.c                       | 12 ++++
 gas/testsuite/gas/riscv/csr-dw-regnums.d    | 17 +++++
 gas/testsuite/gas/riscv/csr-dw-regnums.s    | 18 +++++
 gas/testsuite/gas/riscv/csr-version-1p10.d  | 34 ++++++++++
 gas/testsuite/gas/riscv/csr-version-1p10.l  | 74 +++++++++++++++++++++
 gas/testsuite/gas/riscv/csr-version-1p11.d  | 34 ++++++++++
 gas/testsuite/gas/riscv/csr-version-1p11.l  | 74 +++++++++++++++++++++
 gas/testsuite/gas/riscv/csr-version-1p12.d  | 34 ++++++++++
 gas/testsuite/gas/riscv/csr-version-1p12.l  | 74 +++++++++++++++++++++
 gas/testsuite/gas/riscv/csr-version-1p9p1.d | 34 ++++++++++
 gas/testsuite/gas/riscv/csr-version-1p9p1.l | 74 +++++++++++++++++++++
 gas/testsuite/gas/riscv/csr.s               | 19 ++++++
 include/opcode/riscv-opc.h                  | 36 ++++++++++
 14 files changed, 543 insertions(+), 1 deletion(-)


base-commit: 318d3bda5cad124bd11eebb0349d0f183ba625b1
-- 
2.42.0


  parent reply	other threads:[~2023-09-12  1:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-29  1:19 [REVIEW ONLY 0/1] UNRATIFIED RISC-V: Add 'Smclic' extension and its CSRs Tsukasa OI
2022-11-29  1:19 ` [REVIEW ONLY 1/1] " Tsukasa OI
2022-11-29  2:03   ` Palmer Dabbelt
2022-11-29  2:16     ` Tsukasa OI
2022-11-29  2:43       ` Palmer Dabbelt
2023-09-12  1:39 ` Tsukasa OI [this message]
2023-09-12  1:39   ` [REVIEW ONLY v2 1/1] UNRATIFIED RISC-V: Add CLIC extensions with CSRs Tsukasa OI

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.1694482743.git.research_trasio@irq.a4lg.com \
    --to=research_trasio@irq.a4lg.com \
    --cc=binutils@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).