The following removes a bogus assert constraining the uses that
could appear when a built from scalar defs SLP node constrains
code generation in a way so earlier uses of the vector CTOR
components fail to get vectorized. We can't really constrain the
operation such use appears in.
Bootstrapped and tested on x86_64-unknown-linux-gnu, pushed.
PR tree-optimization/112366
* tree-vect-loop.cc (vectorizable_live_operation): Remove
assert.
---
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 3b28c826b3b..2a43176bcfd 100644
--- a/gcc/tree-vect-loop.cc
+++ b/gcc/tree-vect-loop.cc
@@ -10778,7 +10778,7 @@ vectorizable_live_operation (vec_info *vinfo,
stmt_vec_info stmt_info,
|| !PURE_SLP_STMT (vect_stmt_to_vectorize (use_stmt_info))))
{
/* ??? This can happen when the live lane ends up being
- used in a vector construction code-generated by an
+ rooted in a vector construction code-generated by an
external SLP node (and code-generation for that already
happened). See gcc.dg/vect/bb-slp-47.c.
Doing this is what would happen if that vector CTOR
@@ -10791,11 +10791,6 @@ vectorizable_live_operation (vec_info *vinfo,
stmt_vec_info stmt_info,
&& !vect_stmt_dominates_stmt_p (SSA_NAME_DEF_STMT (new_tree),
use_stmt))
{
- enum tree_code code = gimple_assign_rhs_code (use_stmt);
- gcc_checking_assert (code == SSA_NAME
- || code == CONSTRUCTOR
- || code == VIEW_CONVERT_EXPR
- || CONVERT_EXPR_CODE_P (code));
if (dump_enabled_p ())
dump_printf_loc (MSG_MISSED_OPTIMIZATION, vect_location,
"Using original scalar computation for "
--
2.35.3
