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>
Cc: binutils@sourceware.org
Subject: [REVIEW ONLY 0/2] NEAR RATIFICATION RISC-V: Extensions from the RISC-V Profiles
Date: Thu,  3 Nov 2022 12:26:27 +0000	[thread overview]
Message-ID: <cover.1667478033.git.research_trasio@irq.a4lg.com> (raw)

Hello,

This patchset implements all extensions from RISC-V Profiles (but not
profile itself).  I'm not sure whether this patchset helps someone
implementing RISC-V Profiles but I hope so.

Thanks,
Tsukasa




Tsukasa OI (2):
  NEAR-RATIFICATION RISC-V: Add 'Ssstateen' extension and its CSRs
  NEAR-RATIFICATION RISC-V: Add platform property/capability extensions

 bfd/elfxx-riscv.c                           | 38 +++++++++++++++-
 gas/config/tc-riscv.c                       | 20 +++++----
 gas/testsuite/gas/riscv/csr-version-1p10.l  | 48 ++++++++++-----------
 gas/testsuite/gas/riscv/csr-version-1p11.l  | 48 ++++++++++-----------
 gas/testsuite/gas/riscv/csr-version-1p12.l  | 48 ++++++++++-----------
 gas/testsuite/gas/riscv/csr-version-1p9p1.l | 48 ++++++++++-----------
 gas/testsuite/gas/riscv/csr.s               |  2 +-
 gas/testsuite/gas/riscv/smstateen-csr-s.d   | 22 ++++++++++
 gas/testsuite/gas/riscv/ssstateen-csr.d     | 22 ++++++++++
 gas/testsuite/gas/riscv/ssstateen-csr.s     | 13 ++++++
 include/opcode/riscv-opc.h                  | 26 +++++------
 11 files changed, 215 insertions(+), 120 deletions(-)
 create mode 100644 gas/testsuite/gas/riscv/smstateen-csr-s.d
 create mode 100644 gas/testsuite/gas/riscv/ssstateen-csr.d
 create mode 100644 gas/testsuite/gas/riscv/ssstateen-csr.s


base-commit: ae1c45ead6b60ef0fd338bbeb6a4c5e5808c6e6a
-- 
2.37.2


             reply	other threads:[~2022-11-03 12:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-03 12:26 Tsukasa OI [this message]
2022-11-03 12:26 ` [REVIEW ONLY 1/2] NEAR-RATIFICATION RISC-V: Add 'Ssstateen' extension and its CSRs Tsukasa OI
2022-11-03 12:26 ` [REVIEW ONLY 2/2] NEAR-RATIFICATION RISC-V: Add platform property/capability extensions Tsukasa OI
2022-11-03 13:11 ` [REVIEW ONLY 0/2] NEAR RATIFICATION RISC-V: Extensions from the RISC-V Profiles Nelson Chu
2022-11-03 13:20   ` Tsukasa OI
2022-11-19  2:56   ` Tsukasa OI
2023-01-30  6:35 ` [PATCH v2 0/1] " Tsukasa OI
2023-01-30  6:35   ` [PATCH v2 1/1] RISC-V: Add platform property/capability extensions Tsukasa OI
2023-01-30  7:11   ` [PATCH v3 0/1] RISC-V: Extensions from the RISC-V Profiles Tsukasa OI
2023-01-30  7:11     ` [PATCH v3 1/1] RISC-V: Add platform property/capability extensions Tsukasa OI
2023-07-26  0:05     ` [PATCH v4 0/1] RISC-V: Extensions from the RISC-V Profiles Tsukasa OI
2023-07-26  0:05       ` [PATCH v4 1/1] RISC-V: Add platform property/capability extensions Tsukasa OI
2023-07-26  0:47         ` Palmer Dabbelt
2023-07-26  1:02           ` Tsukasa OI
2023-07-31  2:56           ` Tsukasa OI
2023-01-31  4:46   ` [PATCH v2 0/1] RISC-V: Extensions from the RISC-V Profiles 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.1667478033.git.research_trasio@irq.a4lg.com \
    --to=research_trasio@irq.a4lg.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).