public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Sandiford <richard.sandiford@arm.com>
To: 钟居哲 <juzhe.zhong@rivai.ai>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,  rguenther <rguenther@suse.de>
Subject: Re: [PATCH V14] VECT: Add decrement IV iteration loop control by variable amount support
Date: Wed, 24 May 2023 21:05:01 +0100	[thread overview]
Message-ID: <mpto7m9cx76.fsf@arm.com> (raw)
In-Reply-To: <01AC8631C2D651E1+2023052500374920817146@rivai.ai> (=?utf-8?B?IumSn+WxheWTsiIncw==?= message of "Thu, 25 May 2023 00:37:49 +0800")

I'll look at the samples tomorrow, but just to address one thing:

钟居哲 <juzhe.zhong@rivai.ai> writes:
>>> What gives the best code in these cases?  Is emitting a multiplication
>>> better?  Or is using a new IV better?
> Could you give me more detail information about "new refresh IV" approach.
> I'd like to try that.

By “using a new IV” I meant calling vect_set_loop_controls_directly
for every rgroup, not just the first.  So in the earlier example,
there would be one decrementing IV for x and one decrementing IV for y.

Thanks,
Richard



  reply	other threads:[~2023-05-24 20:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-24 14:48 juzhe.zhong
2023-05-24 15:07 ` Richard Sandiford
2023-05-24 15:13   ` 钟居哲
2023-05-24 15:31     ` Richard Sandiford
2023-05-24 15:42       ` 钟居哲
2023-05-24 15:47         ` Richard Sandiford
2023-05-24 15:52           ` 钟居哲
2023-05-24 16:00             ` Richard Sandiford
2023-05-24 16:15               ` 钟居哲
2023-05-24 16:37               ` 钟居哲
2023-05-24 20:05                 ` Richard Sandiford [this message]
2023-05-25  3:05                   ` juzhe.zhong
     [not found]   ` <2023052423130398041121@rivai.ai>
2023-05-24 15:31     ` 回复: " 钟居哲

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=mpto7m9cx76.fsf@arm.com \
    --to=richard.sandiford@arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=juzhe.zhong@rivai.ai \
    --cc=rguenther@suse.de \
    /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).