public inbox for
 help / color / mirror / Atom feed
From: Tsukasa OI <>
To: Nelson Chu <>, Binutils <>
Subject: Re: [PATCH v3] RISC-V: Add Zawrs ISA extension support
Date: Fri, 23 Sep 2022 16:13:34 +0900	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 2022/09/23 13:34, Nelson Chu wrote:
> On Sun, Sep 18, 2022 at 4:20 PM Tsukasa OI via Binutils
> <> wrote:
>> Functionally, this is good as is.
>> For formatting, there is a small room for further improvements (as I
>> comment below).  This is not your fault but because of my recently
>> upstreamed 'Zmmul' patchset.
> The extension orders in the riscv_supported_* tables are not really
> important for now.  For the single letter standard extensions, the
> order is kept in the riscv_ext_canonical_order.  All extensions should
> be arranged to the correct places by calling riscv_lookup_subset and
> riscv_compare_subsets, and all rules of order are mentioned in the
> riscv_compare_subsets.  So make them in order just for tidy, but won't
> break anything.  The problem we met for the zmmul is g's imply.  The
> order in the riscv_implicit_subsets really matters based on the
> current implementation, and not sure if we will have another choice to
> remove the order limitation when adding implicit extensions.

Yep, just for tidying (and I said "functionally" good).  And I didn't
pointed that 'Zmmul' broke something in that mail.

Because 'Zmmul' is upstreamed after his 'Zawrs' PATCH v2 and 'Zmmul' is
(supposed to be) placed next to 'Zawrs', it caused extension order
different from the canonical ordering while rebasing, that's it.



Talking of 'G' -> 'Zmmul' issue I accidentally created...
I made a script to prevent that from happening again.  It's a hack
(sensitive to code formatting) but works perfectly.  It checks (A -> B)
-> (B -> X) -> (A -> X) for all extensions A, B and X ("->": imply).
It reported 'G' -> 'Zmmul' related error just after my 'Zmmul' patchset
and reported no errors on the latest master.


> Anyway, the v4 patch looks good and approved, so please commit it when
> you think it's time.
> Thanks
> Nelson

      reply	other threads:[~2022-09-23  7:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-18  8:07 Christoph Muellner
2022-09-18  8:19 ` Tsukasa OI
2022-09-23  4:34   ` Nelson Chu
2022-09-23  7:13     ` Tsukasa OI [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).