From: Tsukasa OI <research_trasio@irq.a4lg.com>
To: Andrew Waterman <andrew@sifive.com>
Cc: Palmer Dabbelt <palmer@dabbelt.com>,
Kito Cheng <kito.cheng@sifive.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 1/1] RISC-V: Fix canonical extension order (K and J)
Date: Sun, 24 Apr 2022 15:09:30 +0900 [thread overview]
Message-ID: <9d978145-1400-b281-fbc1-2adabed98cd1@irq.a4lg.com> (raw)
In-Reply-To: <CA++6G0DWhgQ1E5OLhJcvnxcb25ES-Tr-qmH-=ZAbAh27kiX46w@mail.gmail.com>
Hello,
> Neither K nor J is an extension that exists,
That is correct.
> and so it doesn't make
> sense to mandate any particular ordering.
No. It affects Z* extension ordering...
On 2022/04/24 14:36, Andrew Waterman wrote:
> Neither K nor J is an extension that exists, and so it doesn't make
> sense to mandate any particular ordering. The better change would be
> to delete the letters `k' and `j' from that string, so that we aren't
> enforcing constraints that don't serve a useful purpose.
>
> cf. https://github.com/riscv/riscv-isa-manual/commit/f5f9c27010b69a015958ffebe1ac5a34f8776dff
Wait... so, you make constraints for existing single-letters (Zi -> Zv)
but not for non-existing single-letters? (Zk -> Zj, Zj -> Zk) anymore?
That's completely unexpected move but also makes sense.
Let me check your intentions and details: do we need to place Z[CH]*
extensions without single-letter extension [CH] after all existing ones
(like Zv*)? Or, Z[CH]* extensions without single-letter extension [CH]
have no constraints as long as all Z* extensions are grouped together?
>
> On Sat, Apr 23, 2022 at 10:26 PM Tsukasa OI via Gcc-patches
> <gcc-patches@gcc.gnu.org> wrote:
>>
>> This commit fixes canonical extension order to follow the RISC-V ISA
>> Manual draft-20210402-1271737 or later.
>>
>> gcc/ChangeLog:
>>
>> * common/config/riscv/riscv-common.cc (riscv_supported_std_ext):
>> Fix "K" extension prefix to be placed before "J".
>> ---
>> gcc/common/config/riscv/riscv-common.cc | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/gcc/common/config/riscv/riscv-common.cc b/gcc/common/config/riscv/riscv-common.cc
>> index 1501242e296..0b0ec2c4ec5 100644
>> --- a/gcc/common/config/riscv/riscv-common.cc
>> +++ b/gcc/common/config/riscv/riscv-common.cc
>> @@ -594,7 +594,7 @@ riscv_subset_list::lookup (const char *subset, int major_version,
>> static const char *
>> riscv_supported_std_ext (void)
>> {
>> - return "mafdqlcbjktpvn";
>> + return "mafdqlcbkjtpvn";
>> }
>>
>> /* Parsing subset version.
>> --
>> 2.32.0
>>
>
next prev parent reply other threads:[~2022-04-24 6:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-24 5:24 [PATCH 0/1] " Tsukasa OI
2022-04-24 5:24 ` [PATCH 1/1] " Tsukasa OI
2022-04-24 5:36 ` Andrew Waterman
2022-04-24 6:09 ` Tsukasa OI [this message]
2022-04-25 3:33 ` Kito Cheng
2022-04-25 3:35 ` [PATCH 0/1] " Kito Cheng
[not found] <mhng-7946e868-60b9-4160-9d9d-33fa091ea4a0@palmer-ri-x1c9>
[not found] ` <mhng-11cb0b1b-822a-4c04-b1c3-2fe2b3666e24@palmer-mbp2014>
[not found] ` <CAJYME4HZhSZYbLDeX4jkciaFAff2fRRAKMB+mb-n=5ZC0EwWXQ@mail.gmail.com>
2022-05-22 9:35 ` [PATCH 1/1] " 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=9d978145-1400-b281-fbc1-2adabed98cd1@irq.a4lg.com \
--to=research_trasio@irq.a4lg.com \
--cc=andrew@sifive.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=kito.cheng@sifive.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).