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 middle-end/114196] [13/14 Regression] Fixed length vector ICE: in vect_peel_nonlinear_iv_init, at tree-vect-loop.cc:9454
Date: Thu, 07 Mar 2024 20:03:44 +0000	[thread overview]
Message-ID: <bug-114196-4-V6ynYTYuvV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114196-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Robin Dapp <rdapp@gcc.gnu.org>:

https://gcc.gnu.org/g:226043a4d8fb23c7fe7bf16e485b3cfaa094db21

commit r14-9366-g226043a4d8fb23c7fe7bf16e485b3cfaa094db21
Author: Robin Dapp <rdapp@ventanamicro.com>
Date:   Wed Mar 6 16:54:35 2024 +0100

    vect: Do not peel epilogue for partial vectors.

    r14-7036-gcbf569486b2dec added an epilogue vectorization guard for early
    break but PR114196 shows that we also run into the problem without early
    break.  Therefore merge the condition into the topmost vectorization
    guard.

    gcc/ChangeLog:

            PR middle-end/114196

            * tree-vect-loop-manip.cc (vect_can_peel_nonlinear_iv_p): Merge
            vectorization guards.

    gcc/testsuite/ChangeLog:

            * gcc.target/aarch64/pr114196.c: New test.
            * gcc.target/riscv/rvv/autovec/pr114196.c: New test.

  parent reply	other threads:[~2024-03-07 20:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-01 21:35 [Bug middle-end/114196] New: " patrick at rivosinc dot com
2024-03-02  2:02 ` [Bug middle-end/114196] " pinskia at gcc dot gnu.org
2024-03-06 16:09 ` rdapp at gcc dot gnu.org
2024-03-07 20:03 ` cvs-commit at gcc dot gnu.org [this message]
2024-03-08 17:43 ` patrick at rivosinc dot com
2024-03-08 17:44 ` patrick at rivosinc dot com
2024-03-09  7:34 ` [Bug middle-end/114196] [13 " law at gcc dot gnu.org
2024-05-08 12:25 ` rguenth at gcc dot gnu.org
2024-05-13  6:23 ` rdapp at gcc dot gnu.org
2024-05-21  9:19 ` jakub 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-114196-4-V6ynYTYuvV@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).