From: Richard Biener <rguenther@suse.de>
To: Richard Sandiford <richard.sandiford@arm.com>
Cc: juzhe.zhong@rivai.ai, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH V16] VECT: Add decrement IV iteration loop control by variable amount support
Date: Thu, 25 May 2023 13:06:23 +0000 (UTC) [thread overview]
Message-ID: <nycvar.YFH.7.77.849.2305251306080.4723@jbgna.fhfr.qr> (raw)
In-Reply-To: <mptmt1sa8q0.fsf@arm.com>
On Thu, 25 May 2023, Richard Sandiford wrote:
> This looks good to me. Just a couple of very minor cosmetic things:
>
> juzhe.zhong@rivai.ai writes:
> > @@ -753,17 +846,35 @@ vect_set_loop_condition_partial_vectors (class loop *loop,
> > continue;
> > }
> >
> > - /* See whether zero-based IV would ever generate all-false masks
> > - or zero length before wrapping around. */
> > - bool might_wrap_p = vect_rgroup_iv_might_wrap_p (loop_vinfo, rgc);
> > -
> > - /* Set up all controls for this group. */
> > - test_ctrl = vect_set_loop_controls_directly (loop, loop_vinfo,
> > - &preheader_seq,
> > - &header_seq,
> > - loop_cond_gsi, rgc,
> > - niters, niters_skip,
> > - might_wrap_p);
> > + if (!LOOP_VINFO_USING_DECREMENTING_IV_P (loop_vinfo) || !iv_rgc
> > + || (iv_rgc->max_nscalars_per_iter * iv_rgc->factor
> > + != rgc->max_nscalars_per_iter * rgc->factor))
>
> Coding style is to put each subcondition on a separate line when the
> whole condition doesn't fit on a single line. So:
>
> if (!LOOP_VINFO_USING_DECREMENTING_IV_P (loop_vinfo)
> || !iv_rgc
> || (iv_rgc->max_nscalars_per_iter * iv_rgc->factor
> != rgc->max_nscalars_per_iter * rgc->factor))
>
> > @@ -2725,6 +2726,17 @@ start_over:
> > && !vect_verify_loop_lens (loop_vinfo))
> > LOOP_VINFO_CAN_USE_PARTIAL_VECTORS_P (loop_vinfo) = false;
> >
> > + /* If we're vectorizing an loop that uses length "controls" and
>
> s/an loop/a loop/ (Sorry for not noticing earlier.)
>
> OK for trunk from my POV with those changes; no need to repost unless
> your policies require it. Please give Richi a chance to comment too
> though.
LGTM as well.
Thanks,
Richard.
next prev parent reply other threads:[~2023-05-25 13:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-25 12:05 juzhe.zhong
2023-05-25 12:36 ` Richard Sandiford
2023-05-25 12:43 ` 钟居哲
2023-05-25 13:06 ` Richard Biener [this message]
2023-05-25 14:49 ` Li, Pan2
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.2305251306080.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).