From: Tsukasa OI <research_trasio@irq.a4lg.com>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: binutils@sourceware.org
Subject: Re: [PATCH v4 1/1] RISC-V: Add platform property/capability extensions
Date: Wed, 26 Jul 2023 10:02:24 +0900 [thread overview]
Message-ID: <55dbb1be-45f7-0784-cbd3-c33e43cabbb1@irq.a4lg.com> (raw)
In-Reply-To: <mhng-1edc0335-db7a-4a45-a972-ff69c3726428@palmer-ri-x1c9a>
On 2023/07/26 9:47, Palmer Dabbelt wrote:
> IMO we want to stay away from these extensions that are just defined by
> a single phrase in the spec. We're still digging out from the first
> rounds of changed specs, trying to start supporting stuff that's not
> even been defined is going to just make for another round of headaches.
I see. I don't completely agree but it makes sense ('Zkt' for example,
has a dedicated section to describe this extension).
I think there's not so much room for improvements for many of "single
phrase" extensions (on 'Ssu64xl', I requested to clarify some details
before the ratification; 'Zic64b' describes itself completely and adding
more words won't work; definition of 'Zicclsm' on the other hand, might
be better to be a bit stricter). However, I see they are not so urgent.
As long as this patch set is considered as a prerequisite of further
"RISC-V Profiles" support (e.g. "-march=rva..."), I can wait.
Thanks,
Tsukasa
next prev parent reply other threads:[~2023-07-26 1:02 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 RISC-V: Extensions from the RISC-V Profiles 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 ` [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 [this message]
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=55dbb1be-45f7-0784-cbd3-c33e43cabbb1@irq.a4lg.com \
--to=research_trasio@irq.a4lg.com \
--cc=binutils@sourceware.org \
--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).