public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Richard Biener <rguenth@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-6570] [PATCH v2] vect: Check that vector factor is a compile-time constant Date: Fri, 10 Mar 2023 07:20:57 +0000 (GMT) [thread overview] Message-ID: <20230310072057.717353858C54@sourceware.org> (raw) https://gcc.gnu.org/g:2dc73876fc9a0df4c3af2766319402d14d39db33 commit r13-6570-g2dc73876fc9a0df4c3af2766319402d14d39db33 Author: Michael Collison <collison@rivosinc.com> Date: Fri Mar 10 08:19:04 2023 +0100 [PATCH v2] vect: Check that vector factor is a compile-time constant * tree-vect-loop-manip.cc (vect_do_peeling): Use result of constant_lower_bound instead of vf for the lower bound of the epilog loop trip count. Diff: --- gcc/tree-vect-loop-manip.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gcc/tree-vect-loop-manip.cc b/gcc/tree-vect-loop-manip.cc index d88edafa018..f60fa50e8f4 100644 --- a/gcc/tree-vect-loop-manip.cc +++ b/gcc/tree-vect-loop-manip.cc @@ -2921,7 +2921,7 @@ vect_do_peeling (loop_vec_info loop_vinfo, tree niters, tree nitersm1, if (new_var_p) { value_range vr (type, - wi::to_wide (build_int_cst (type, vf)), + wi::to_wide (build_int_cst (type, lowest_vf)), wi::to_wide (TYPE_MAX_VALUE (type))); set_range_info (niters, vr); }
reply other threads:[~2023-03-10 7:20 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230310072057.717353858C54@sourceware.org \ --to=rguenth@gcc.gnu.org \ --cc=gcc-cvs@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).