public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "linkw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/103196] [12 regression] gcc.target/powerpc/p9-vec-length-full-7.c
Date: Fri, 25 Feb 2022 08:48:47 +0000	[thread overview]
Message-ID: <bug-103196-4-GI1d4BmJU7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103196-4@http.gcc.gnu.org/bugzilla/>

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

Kewen Lin <linkw at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|                            |2022-02-25
             Status|UNCONFIRMED                 |ASSIGNED
     Ever confirmed|0                           |1

--- Comment #3 from Kewen Lin <linkw at gcc dot gnu.org> ---
The extra stxvl instructions are from the function with type int8 and uint8.
The commit r12-5129 changes the vectorized loop body slightly, it makes the
later cunroll pass have different estimated sizes for the unrolled loops and
makes different decisions to unroll it completely or not.

such as: for test_npeel_int8_t

before the commit, we have:

  Loop 1 likely iterates at most 3 times.
  size: 8-2, last_iteration: 8-4
    Loop size: 8
    Estimated size after unrolling: 14
  Not unrolling loop 1: size would grow.

right after that, we have:

  Loop 1 likely iterates at most 2 times.
  size: 8-4, last_iteration: 8-4
    Loop size: 8
    Estimated size after unrolling: 8

So the vectorized loop of test_npeel_int8_t gets unrolled completely.

The fix could be to disable pass tree-cunroll for this case.

  parent reply	other threads:[~2022-02-25  8:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-11 17:59 [Bug target/103196] New: " seurer at gcc dot gnu.org
2021-11-12  7:39 ` [Bug target/103196] " rguenth at gcc dot gnu.org
2021-11-12  7:57 ` tnfchris at gcc dot gnu.org
2022-02-24  0:39 ` linkw at gcc dot gnu.org
2022-02-25  8:48 ` linkw at gcc dot gnu.org [this message]
2022-03-09 14:15 ` [Bug testsuite/103196] " rguenth at gcc dot gnu.org
2022-03-10  1:44 ` linkw at gcc dot gnu.org
2022-04-11  2:52 ` cvs-commit at gcc dot gnu.org
2022-04-11  3:25 ` linkw at gcc dot gnu.org

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-103196-4-GI1d4BmJU7@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).