From: Jeff Law <jeffreyalaw@gmail.com>
To: 钟居哲 <juzhe.zhong@rivai.ai>, gcc-patches <gcc-patches@gcc.gnu.org>
Cc: "kito.cheng" <kito.cheng@gmail.com>, palmer <palmer@dabbelt.com>
Subject: Re: [PATCH] RISC-V: Support VSETVL PASS for RVV support
Date: Tue, 27 Dec 2022 11:31:43 -0700 [thread overview]
Message-ID: <0cca02a3-bb7e-3645-d98f-b6c04457ad07@gmail.com> (raw)
In-Reply-To: <4DFC9DE6B54EBF58+20221220065905807562113@rivai.ai>
On 12/19/22 15:59, 钟居哲 wrote:
> >> ISTM that if you want to run before sched2, then
>>> you'd need to introduce dependencies between the vsetvl instrutions and
>>> the vector instructions that utilize those settings?
>
> Yes, I want to run before sched2 so that we could have the chance to do the
> instruction scheduling before sched2. I already introduce dependencies in
> vector instructions so that it won't produce any issues.
Ah good that you're adding the necessary dependencies. We'd been
talking a bit about this internally. The hope is that on an OOO machine
the vsetvl will be able to issue/execute relatively early, but on an
in-order machine the ability to schedule the vsetvl could become
significantly more important.
>
> >> It'd probably be better to move this into rtl.cc with a prototype in
>>>rtl.h rather than have duplicate definitions in gcse.c and the RISC-V
>>>backend. I'm not even entirely sure why we really need it here.
> Maybe we do that when GCC14 is open?
If we're just making a routine external that previously had static scope
then we can still do that IMHO. Such a change won't affect code
generation so it should be extremely safe. I'm happy to engage with
Richi and Jakub to get their sign-off on such a change.
Jeff
next prev parent reply other threads:[~2022-12-27 18:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 7:13 juzhe.zhong
2022-12-19 15:44 ` Jeff Law
2022-12-19 22:59 ` 钟居哲
2022-12-27 18:31 ` Jeff Law [this message]
2022-12-14 7:31 juzhe.zhong
2022-12-14 7:31 juzhe.zhong
2022-12-19 15:12 ` Kito Cheng
2022-12-23 10:53 ` Andreas Schwab
2022-12-23 12:19 ` 钟居哲
2022-12-23 14:54 ` Andreas Schwab
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=0cca02a3-bb7e-3645-d98f-b6c04457ad07@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=juzhe.zhong@rivai.ai \
--cc=kito.cheng@gmail.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).