From: Richard Biener <rguenther@suse.de>
To: Richard Sandiford <richard.sandiford@arm.com>
Cc: 钟居哲 <juzhe.zhong@rivai.ai>, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH V12] VECT: Add decrement IV iteration loop control by variable amount support
Date: Wed, 24 May 2023 12:51:13 +0000 (UTC) [thread overview]
Message-ID: <nycvar.YFH.7.77.849.2305241249320.4723@jbgna.fhfr.qr> (raw)
In-Reply-To: <mptedn5hpf3.fsf@arm.com>
On Wed, 24 May 2023, Richard Sandiford wrote:
> Sorry, I realised later that I had an implicit assumption here:
> if there are multiple rgroups, it's better to have a single IV
> for the smallest rgroup and scale that up to bigger rgroups.
>
> E.g. if the loop control IV is taken from an N-control rgroup
> and has a step S, an N*M-control rgroup would be based on M*S.
>
> Of course, it's also OK to create multiple IVs if you prefer.
> It's just a question of which approach gives the best output
> in practice.
One thing to check is whether IVOPTs is ever able to eliminate
one such IV using another. You can then also check whether
when presented with a single IV it already considers the
others you can create as candidates so you get the optimal
selection in the end.
Richard.
next prev parent reply other threads:[~2023-05-24 12:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 8:38 juzhe.zhong
2023-05-23 12:32 ` juzhe.zhong
2023-05-24 11:23 ` Richard Sandiford
2023-05-24 11:52 ` 钟居哲
2023-05-24 12:41 ` Richard Sandiford
2023-05-24 12:51 ` Richard Biener [this message]
2023-05-24 13:27 ` 钟居哲
2023-05-24 13:26 ` 钟居哲
2023-05-24 14:01 ` Richard Sandiford
2023-05-24 14:10 ` 钟居哲
2023-05-24 14:57 ` Richard Sandiford
2023-05-24 14:58 ` 钟居哲
[not found] ` <2023052422100415521814@rivai.ai>
2023-05-24 14:11 ` 钟居哲
2023-05-24 14:22 ` 钟居哲
2023-05-24 14:35 ` 钟居哲
2023-05-24 12:19 ` 钟居哲
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=nycvar.YFH.7.77.849.2305241249320.4723@jbgna.fhfr.qr \
--to=rguenther@suse.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=juzhe.zhong@rivai.ai \
--cc=richard.sandiford@arm.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).