From: Lehua Ding <lehua.ding@rivai.ai>
To: Robin Dapp <rdapp.gcc@gmail.com>, gcc-patches@gcc.gnu.org
Cc: juzhe.zhong@rivai.ai, kito.cheng@gmail.com, palmer@rivosinc.com,
jeffreyalaw@gmail.com
Subject: Re: [PATCH V3] RISC-V: Support combine cond extend and reduce sum to widen reduce sum
Date: Fri, 22 Sep 2023 11:03:17 +0800 [thread overview]
Message-ID: <6FBEFA8C8770B4FE+4dc29192-1d9d-44f3-b5f9-4576e2afdb28@rivai.ai> (raw)
In-Reply-To: <3C6AA492E5801A6E+bfd50225-ccd5-4eb7-b4b7-2831687d6ccd@rivai.ai>
Committed with splited patchs, thanks Robin.
[COMMITTED] RISC-V: Split VLS avl_type from NONVLMAX avl_type
https://gcc.gnu.org/pipermail/gcc-patches/2023-September/631152.html
[COMMITTED V4] RISC-V: Support combine cond extend and reduce sum to
widen reduce sum
https://gcc.gnu.org/pipermail/gcc-patches/2023-September/631153.html
On 2023/9/21 16:27, Lehua Ding wrote:
> Hi Robin,
>
> On 2023/9/21 16:12, Robin Dapp wrote:
>> Hi Lehua,
>>
>>> V3 Change: Back to the original method.
>> Was there an original method even before the first patch?
>
> Yes, this was the method that came to mind at first, and I didn't send a
> patch because I didn't feel like the pattern looked good :)
>
>> Anyway, I prefer this v3 over the others even though the large
>> pattern is not exactly pretty :)
>>
>> What about the VLS changes? Are they necessary for the patterns/tests?
>> I mean they are reasonable in themselves but are they related?
>> If so, please specify. If not please split them off into a small
>> (pre-approved) patch. OK with this adjusted.
>
> This VLS change is necessary for the patch and only used by this patch
> currently. Currently, VLMAX inside avl_type stands for VLA mode using
> VLMAX, however, we need to distinguish from NONVLMAX in the case where
> the vl is the number of units of the mode. This way it is safe and
> simple to do combine. Therefore a new avl_type enumeration VLS is
> introduced to distinguish.
>
> There's an overlap between VLMAX and VLS here, and it's probably more
> appropriate to use FULL or something similar, like the other patch that
> changes the comments. I'm going to hold off on making any major changes
> for now, though, as the impact is more localized.
>
--
Best,
Lehua (RiVAI)
lehua.ding@rivai.ai
prev parent reply other threads:[~2023-09-22 3:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 5:32 Lehua Ding
2023-09-21 8:12 ` Robin Dapp
2023-09-21 8:27 ` Lehua Ding
2023-09-22 3:03 ` Lehua Ding [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:
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=6FBEFA8C8770B4FE+4dc29192-1d9d-44f3-b5f9-4576e2afdb28@rivai.ai \
--to=lehua.ding@rivai.ai \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=juzhe.zhong@rivai.ai \
--cc=kito.cheng@gmail.com \
--cc=palmer@rivosinc.com \
--cc=rdapp.gcc@gmail.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).