From: Tsukasa OI <research_trasio@irq.a4lg.com>
To: Nelson Chu <nelson.chu@sifive.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: [PATCH 1/2] RISC-V: Add 'H' to canonical extension ordering
Date: Wed, 22 Jun 2022 20:08:25 +0900 [thread overview]
Message-ID: <173ed92f-1492-3a42-809b-952279a52507@irq.a4lg.com> (raw)
In-Reply-To: <CAJYME4Ec=Zv2RNET30Qf7p9S38TB_g2m=x7-Wa6uyQ0KQDZ7xw@mail.gmail.com>
On 2022/06/22 19:39, Nelson Chu wrote:
> Sorry for being late, I have been busy recently. I didn't notice that
> the isa spec had been updated, anyway, the h is a single extension
> after v, rather than the multi-letter extension for now. So LGTM,
> committed.
>
> Besides, please give me some time to review other patches, I've been
> busy with other things for a while...
Merging smallest one will be great but I understand the situation.
Besides, some of my patchsets are not only large but complex.
And... since you added 'H' support to GNU Binutils, I think I need to
rewrite my old CSR patchset (yes, it's going to be big).
Anyway, I will submit following patchsets later (so you don't need
patchsets below until I submit newer ones):
1a. Combined floating point enhancements and fixes
1b. Minimal Zfinx fixes (incompatible with 1a)
2. CSR addition (Smstateen/Sscofpmf/Sstc)
Thanks,
Tsukasa
>
> Thanks
> Nelson
>
> On Sun, Jun 5, 2022 at 12:43 PM Tsukasa OI <research_trasio@irq.a4lg.com> wrote:
>>
>> This commit adds 'H' to canonical extension ordering based on current
>> consensus (not officially ratified as a new ISA specification manual
>> but discussion for software compatibility is made).
>>
>> bfd/ChangeLog
>>
>> * elfxx-riscv.c (riscv_ext_canonical_order): Add 'H' for
>> canonical extension ordering based on current consensus.
>> ---
>> bfd/elfxx-riscv.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/bfd/elfxx-riscv.c b/bfd/elfxx-riscv.c
>> index 92ad03feea0..5c2c616a760 100644
>> --- a/bfd/elfxx-riscv.c
>> +++ b/bfd/elfxx-riscv.c
>> @@ -1345,7 +1345,7 @@ riscv_recognized_prefixed_ext (const char *ext)
>> }
>>
>> /* Canonical order for single letter extensions. */
>> -static const char riscv_ext_canonical_order[] = "eigmafdqlcbkjtpvn";
>> +static const char riscv_ext_canonical_order[] = "eigmafdqlcbkjtpvnh";
>>
>> /* Array is used to compare the orders of standard extensions quickly. */
>> static int riscv_ext_order[26] = {0};
>> --
>> 2.34.1
>>
>
next prev parent reply other threads:[~2022-06-22 11:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-05 4:43 [PATCH 0/2] RISC-V: QUICK fix on Li's Zhinx implementation Tsukasa OI
2022-06-05 4:43 ` [PATCH 1/2] RISC-V: Add 'H' to canonical extension ordering Tsukasa OI
2022-06-22 10:39 ` Nelson Chu
2022-06-22 11:08 ` Tsukasa OI [this message]
2022-06-05 4:43 ` [PATCH 2/2] RISC-V: Fix requirement handling on Zhinx+{D,Q} Tsukasa OI
2022-06-24 2:59 ` [PATCH v2 0/1] RISC-V: QUICK fix on Li's Zhinx implementation Tsukasa OI
2022-06-24 2:59 ` [PATCH v2 1/1] RISC-V: Fix requirement handling on Zhinx+{D,Q} Tsukasa OI
2022-06-24 3:51 ` [PATCH v3 0/2] RISC-V: QUICK fix on Li's Zhinx implementation Tsukasa OI
2022-06-24 3:51 ` [PATCH v3 1/2] RISC-V: Fix requirement handling on Zhinx+{D,Q} Tsukasa OI
2022-07-07 3:02 ` Kito Cheng
2022-07-07 4:25 ` Nelson Chu
2022-06-24 3:51 ` [PATCH v3 2/2] RISC-V: Reorder Zhinx extension 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=173ed92f-1492-3a42-809b-952279a52507@irq.a4lg.com \
--to=research_trasio@irq.a4lg.com \
--cc=binutils@sourceware.org \
--cc=nelson.chu@sifive.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).