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(refs/users/rguenth/heads/vect-force-slp)] Relax COND_EXPR reduction vectorization SLP restriction Date: Mon, 13 May 2024 14:27:43 +0000 (GMT) [thread overview] Message-ID: <20240513142744.363C83870879@sourceware.org> (raw) https://gcc.gnu.org/g:1ba0215280e51f0cbc3c3867d6e8c07fc76694f8 commit 1ba0215280e51f0cbc3c3867d6e8c07fc76694f8 Author: Richard Biener <rguenther@suse.de> Date: Fri Feb 23 16:16:38 2024 +0100 Relax COND_EXPR reduction vectorization SLP restriction Allow one-lane SLP but for the case where we need to swap the arms. * tree-vect-stmts.cc (vectorizable_condition): Allow single-lane SLP, but not when we need to swap then and else clause. Diff: --- gcc/tree-vect-stmts.cc | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/gcc/tree-vect-stmts.cc b/gcc/tree-vect-stmts.cc index 72a9c144823c..8fef72cb9072 100644 --- a/gcc/tree-vect-stmts.cc +++ b/gcc/tree-vect-stmts.cc @@ -12105,7 +12105,7 @@ vectorizable_condition (vec_info *vinfo, = STMT_VINFO_REDUC_DEF (vect_orig_stmt (stmt_info)) != NULL; if (for_reduction) { - if (slp_node) + if (slp_node && SLP_TREE_LANES (slp_node) > 1) return false; reduc_info = info_for_reduction (vinfo, stmt_info); reduction_type = STMT_VINFO_REDUC_TYPE (reduc_info); @@ -12194,6 +12194,10 @@ vectorizable_condition (vec_info *vinfo, cond_expr = NULL_TREE; } } + /* ??? The vectorized operand query below doesn't allow swapping + this way for SLP. */ + if (slp_node) + return false; std::swap (then_clause, else_clause); }
next reply other threads:[~2024-05-13 14:27 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-13 14:27 Richard Biener [this message] -- strict thread matches above, loose matches on Subject: below -- 2024-02-23 15:18 Richard Biener
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=20240513142744.363C83870879@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).