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-29] tree-optimization/104322 - remove dead code in vectorizable_reduction Date: Fri, 29 Apr 2022 08:16:23 +0000 (GMT) [thread overview] Message-ID: <20220429081623.E7BEF3857433@sourceware.org> (raw) https://gcc.gnu.org/g:7259481f0ece6283a6e2943448e8d28ffffc40f9 commit r13-29-g7259481f0ece6283a6e2943448e8d28ffffc40f9 Author: Richard Biener <rguenther@suse.de> Date: Tue Feb 1 11:32:11 2022 +0100 tree-optimization/104322 - remove dead code in vectorizable_reduction The PR points out dead code after previous refactoring. 2022-02-01 Richard Biener <rguenther@suse.de> PR tree-optimization/104322 * tree-vect-loop.cc (vectorizable_reduction): Remove dead code. Diff: --- gcc/tree-vect-loop.cc | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/gcc/tree-vect-loop.cc b/gcc/tree-vect-loop.cc index f53a634a390..ab7dade1c74 100644 --- a/gcc/tree-vect-loop.cc +++ b/gcc/tree-vect-loop.cc @@ -6634,19 +6634,14 @@ vectorizable_reduction (loop_vec_info loop_vinfo, need it to get at the number of vector stmts which wasn't yet initialized for the instance root. */ } - if (STMT_VINFO_DEF_TYPE (stmt_info) == vect_reduction_def) - stmt_info = vect_stmt_to_vectorize (STMT_VINFO_REDUC_DEF (stmt_info)); - else + if (STMT_VINFO_DEF_TYPE (stmt_info) == vect_double_reduction_def) { - gcc_assert (STMT_VINFO_DEF_TYPE (stmt_info) - == vect_double_reduction_def); use_operand_p use_p; gimple *use_stmt; bool res = single_imm_use (gimple_phi_result (stmt_info->stmt), &use_p, &use_stmt); gcc_assert (res); phi_info = loop_vinfo->lookup_stmt (use_stmt); - stmt_info = vect_stmt_to_vectorize (STMT_VINFO_REDUC_DEF (phi_info)); } /* PHIs should not participate in patterns. */
reply other threads:[~2022-04-29 8:16 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=20220429081623.E7BEF3857433@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).