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: [PATCH v4 0/1] RISC-V: Extensions from the RISC-V Profiles
Date: Wed, 26 Jul 2023 00:05:52 +0000 [thread overview]
Message-ID: <cover.1690329932.git.research_trasio@irq.a4lg.com> (raw)
In-Reply-To: <cover.1675062682.git.research_trasio@irq.a4lg.com>
This patch (set) adds 7 unprivileged extensions and 13 privileged
extensions, all of which denotes certain platform capability / constraint.
This is almost a resend of the previous PATCH v3 (in January 2023) but since
the RISC-V Profiles specification is now ratified, it's much safer to merge.
[Changes: v2 -> v3]
1. After AIA is upstreamed, I haven't done tidying up with
riscv_supported_std_s_ext with my rebased branch. That made location of
'Ssaia' a bit out of place. PATCH v3 fixes this.
2. After version 0.8, the new extension 'Sscounterenw' is added but I
missed that. PATCH v3 adds support for this new extension correctly.
3. I made minor changes to ChangeLog part of the commit message
(I moved 'H' -> 'Zicsr' dependency for a reason but I didn't mentioned
in the ChangeLog).
[Changes: v3 -> v4]
1. Rebase against the latest master (with a bit of reordering).
2. Reorder renamed 'Svade' to reflect canonical order.
3. Referenced specification is now the ratified one (version 1.0),
not frozen but draft one (version 0.9.2).
Thanks,
Tsukasa
Tsukasa OI (1):
RISC-V: Add platform property/capability extensions
bfd/elfxx-riscv.c | 35 ++++++++++++++++++++++++++++++++++-
1 file changed, 34 insertions(+), 1 deletion(-)
base-commit: 6296109afcd8c8e89b771fbaf092d17a17d4ea99
--
2.41.0
next prev parent reply other threads:[~2023-07-26 0:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 12:26 [REVIEW ONLY 0/2] NEAR RATIFICATION " Tsukasa OI
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 ` Tsukasa OI [this message]
2023-07-26 0:05 ` [PATCH v4 " 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.1690329932.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).