From: Tsukasa OI <research_trasio@irq.a4lg.com>
To: Nelson Chu <nelson@rivosinc.com>
Cc: binutils@sourceware.org
Subject: Re: [REVIEW ONLY 0/2] NEAR RATIFICATION RISC-V: Extensions from the RISC-V Profiles
Date: Thu, 3 Nov 2022 22:20:24 +0900 [thread overview]
Message-ID: <0b7998c5-c186-ca90-3164-d9ae81295154@irq.a4lg.com> (raw)
In-Reply-To: <CAPpQWtBi5mRGEE2oanX_8mMi-s1yYwQJm98LWg2j-CdsaDoeeg@mail.gmail.com>
On 2022/11/03 22:11, Nelson Chu wrote:
> On Thu, Nov 3, 2022 at 8:26 PM Tsukasa OI <research_trasio@irq.a4lg.com> wrote:
>>
>> 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
>
> Looks good.
>
>> NEAR-RATIFICATION RISC-V: Add platform property/capability extensions
>
> If we just need to recognize them in assembler, then it looks good.
> Thanks for arranging these bunch of extensions before everything gets
> messy... Generally, since they are frozen, we have good reason to
> commit them to the mainline. But if you prefer to wait until they are
> ratified, then that's also work to me, I believe you know when will be
> the best time, so please commit at that time.
Thanks for the review!
I want to clarify that whether those names are actually extensions and I
just pushed a pull request for this (related to PATCH 2/2):
<https://github.com/riscv/riscv-profiles/pull/76>
I will push this depending on the resolution of this pull request.
Thanks,
Tsukasa
>
> Thanks
> Nelson
>
> Nelson
>
>> 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
>>
>
next prev parent reply other threads:[~2022-11-03 13:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 12:26 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 [this message]
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=0b7998c5-c186-ca90-3164-d9ae81295154@irq.a4lg.com \
--to=research_trasio@irq.a4lg.com \
--cc=binutils@sourceware.org \
--cc=nelson@rivosinc.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).