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/106963] [13 Regression] ICE in vect_gen_perm_mask_checked, at tree-vect-stmts.cc:8606 since r13-2503-gc13223b790bbc5e4 Date: Wed, 21 Sep 2022 07:48:00 +0000 [thread overview] Message-ID: <bug-106963-4-1QK04puZCe@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106963-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106963 --- Comment #3 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:eddbb81f1254f025d6f1b6b8e7554aa9a3830302 commit r13-2754-geddbb81f1254f025d6f1b6b8e7554aa9a3830302 Author: liuhongt <hongtao.liu@intel.com> Date: Tue Sep 20 13:22:28 2022 +0800 Don't check can_vec_perm_const_p for nonlinear iv_init when it's constant. When init_expr is INTEGER_CST or REAL_CST, can_vec_perm_const_p is not necessary since there's no real vec_perm needed, but vec_gen_perm_mask_checked will gcc_assert (can_vec_perm_const_p). So it's better to use vec_gen_perm_mask_any in vect_create_nonlinear_iv_init. gcc/ChangeLog: PR tree-optimization/106963 * tree-vect-loop.cc (vect_create_nonlinear_iv_init): Use vec_gen_perm_mask_any instead of vec_gen_perm_mask_check. gcc/testsuite/ChangeLog: * gcc.target/i386/pr106963.c: New test.
next prev parent reply other threads:[~2022-09-21 7:48 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-18 6:03 [Bug tree-optimization/106963] New: [13 Regression] ICE in vect_gen_perm_mask_checked, at tree-vect-stmts.cc:8606 asolokha at gmx dot com 2022-09-19 6:39 ` [Bug tree-optimization/106963] " rguenth at gcc dot gnu.org 2022-09-20 2:59 ` crazylht at gmail dot com 2022-09-20 8:42 ` [Bug tree-optimization/106963] [13 Regression] ICE in vect_gen_perm_mask_checked, at tree-vect-stmts.cc:8606 since r13-2503-gc13223b790bbc5e4 marxin at gcc dot gnu.org 2022-09-21 7:48 ` cvs-commit at gcc dot gnu.org [this message] 2022-09-21 7:48 ` crazylht at gmail dot com 2022-10-18 8:44 ` 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-106963-4-1QK04puZCe@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).