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/107055] [13 Regression] ICE in vect_peel_nonlinear_iv_init, at tree-vect-loop.cc:8415 Date: Thu, 29 Sep 2022 07:23:34 +0000 [thread overview] Message-ID: <bug-107055-4-Dn2WHycusD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107055-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107055 --- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by hongtao Liu <liuhongt@gcc.gnu.org>: https://gcc.gnu.org/g:f758d447d7f4699253c9f8ee345ba9b8357cdb22 commit r13-2925-gf758d447d7f4699253c9f8ee345ba9b8357cdb22 Author: liuhongt <hongtao.liu@intel.com> Date: Wed Sep 28 17:00:48 2022 +0800 Check nonlinear iv in vect_can_advance_ivs_p. vectorizable_nonlinear_induction doesn't always guard vect_peel_nonlinear_iv_init when it's called by vect_update_ivs_after_vectorizer. It's supposed to be guarded by vect_can_advance_ivs_p. gcc/ChangeLog: PR tree-optimization/107055 * tree-vect-loop-manip.cc (vect_can_advance_ivs_p): Check for nonlinear induction variables. * tree-vect-loop.cc (vect_can_peel_nonlinear_iv_p): New functions. (vectorizable_nonlinear_induction): Put part codes into vect_can_peel_nonlinear_iv_p. * tree-vectorizer.h (vect_can_peel_nonlinear_iv_p): Declare. gcc/testsuite/ChangeLog: * gcc.target/i386/pr107055.c: New test.
next prev parent reply other threads:[~2022-09-29 7:23 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-27 16:22 [Bug c/107055] New: " gscfq@t-online.de 2022-09-27 16:37 ` [Bug tree-optimization/107055] " pinskia at gcc dot gnu.org 2022-09-28 5:14 ` crazylht at gmail dot com 2022-09-28 7:01 ` crazylht at gmail dot com 2022-09-28 8:41 ` crazylht at gmail dot com 2022-09-28 8:42 ` crazylht at gmail dot com 2022-09-29 7:23 ` cvs-commit at gcc dot gnu.org [this message] 2022-09-29 7:24 ` crazylht at gmail dot com 2022-09-29 7:59 ` rguenth 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-107055-4-Dn2WHycusD@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: linkBe 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).