public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/110449] Vect: use a small step to calculate the loop induction if the loop is unrolled during loop vectorization
Date: Thu, 06 Jul 2023 16:05:31 +0000	[thread overview]
Message-ID: <bug-110449-4-S1940LoV4X@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110449-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110449

--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jeff Law <law@gcc.gnu.org>:

https://gcc.gnu.org/g:224fd59b2dc8a5fa78a309a09863afe9b3cf2111

commit r14-2367-g224fd59b2dc8a5fa78a309a09863afe9b3cf2111
Author: Hao Liu OS <hliu@os.amperecomputing.com>
Date:   Thu Jul 6 10:04:46 2023 -0600

    Vect: use a small step to calculate induction for the unrolled loop (PR
tree-optimization/110449)

    If a loop is unrolled by n times during vectoriation, two steps are used to
    calculate the induction variable:
      - The small step for the unrolled ith-copy: vec_1 = vec_iv + (VF/n *
Step)
      - The large step for the whole loop: vec_loop = vec_iv + (VF * Step)

    This patch calculates an extra vec_n to replace vec_loop:
      vec_n = vec_prev + (VF/n * S) = vec_iv + (VF/n * S) * n = vec_loop.

    So that we can save the large step register and related operations.

    gcc/ChangeLog:

            PR tree-optimization/110449
            * tree-vect-loop.cc (vectorizable_induction): use vec_n to replace
            vec_loop for the unrolled loop.

    gcc/testsuite/ChangeLog:

            * gcc.target/aarch64/pr110449.c: New testcase.

      parent reply	other threads:[~2023-07-06 16:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-28  9:22 [Bug tree-optimization/110449] New: " hliu at amperecomputing dot com
2023-06-28 20:11 ` [Bug tree-optimization/110449] " rsandifo at gcc dot gnu.org
2023-06-29  3:15 ` hliu at amperecomputing dot com
2023-07-06 16:05 ` cvs-commit at gcc dot gnu.org [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=bug-110449-4-S1940LoV4X@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).