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/110474] Vect: the epilog vect loop should have small VF if the loop is unrolled during vectorization
Date: Thu, 06 Jul 2023 02:07:29 +0000	[thread overview]
Message-ID: <bug-110474-4-GQsYXVFwTu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110474-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Hao Liu <hliu@gcc.gnu.org>:

https://gcc.gnu.org/g:7339e725b995912747c01c3ec80ce602512f45df

commit r14-2335-g7339e725b995912747c01c3ec80ce602512f45df
Author: Hao Liu <hliu@os.amperecomputing.com>
Date:   Thu Jul 6 10:03:47 2023 +0800

    tree-optimization/110474 - Vect: select small VF for epilog of unrolled
loop

    If a loop is unrolled during vectorization (i.e. suggested_unroll_factor >
1),
    the VFs of both main and epilog loop are enlarged.  The epilog vect loop is
    specific for a loop with small iteration counts, so a large VF may hurt
    performance.

    This patch unscales the main loop VF by suggested_unroll_factor while
selecting
    the epilog loop VF, so that it will be the same as vectorized loop without
    unrolling (i.e. suggested_unroll_factor = 1).

    gcc/ChangeLog:

            PR tree-optimization/110474
            * tree-vect-loop.cc (vect_analyze_loop_2): unscale the VF by
suggested
            unroll factor while selecting the epilog vect loop VF.

    gcc/testsuite/ChangeLog:

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

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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-29  4:35 [Bug tree-optimization/110474] New: " hliu at amperecomputing dot com
2023-06-29  7:33 ` [Bug tree-optimization/110474] " rguenth at gcc dot gnu.org
2023-07-06  2:07 ` cvs-commit at gcc dot gnu.org [this message]
2023-07-06  2:21 ` hliu at amperecomputing dot com

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-110474-4-GQsYXVFwTu@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).