Lines Matching refs:relevant

198    Mark STMT_INFO as "relevant for vectorization" and add it to WORKLIST.  */
202 enum vect_relevant relevant, bool live_p)
209 "mark relevant %d, live %d: %G", relevant, live_p,
220 as relevant/live because it's not going to be vectorized.
226 " relevant/live.\n");
235 if (relevant > STMT_VINFO_RELEVANT (stmt_info))
236 STMT_VINFO_RELEVANT (stmt_info) = relevant;
243 "already marked relevant/live.\n");
287 is "relevant for vectorization".
289 A stmt is considered "relevant for vectorization" if:
298 enum vect_relevant *relevant, bool *live_p)
306 *relevant = vect_unused_in_scope;
312 *relevant = vect_used_in_scope;
322 *relevant = vect_used_in_scope;
350 if (*live_p && *relevant == vect_unused_in_scope
355 "vec_stmt_relevant_p: stmt live but not relevant.\n");
356 *relevant = vect_used_only_live;
359 return (*live_p || *relevant);
434 the WORKLIST (to add DEF_STMT to the WORKLIST in case it is relevant).
442 STMT_VINFO_RELEVANT (DEF_stmt_vinfo) <-- relevant
450 "relevant" will be modified accordingly.
456 enum vect_relevant relevant, vec<stmt_vec_info> *worklist,
463 that are used for address computation are not considered relevant. */
490 vect_mark_relevant (worklist, dstmt_vinfo, relevant, true);
507 switch (relevant)
510 relevant = (STMT_VINFO_DEF_TYPE (stmt_vinfo) == vect_nested_cycle) ?
516 relevant = vect_used_by_reduction;
521 relevant = vect_used_in_scope;
545 switch (relevant)
548 relevant = (STMT_VINFO_DEF_TYPE (stmt_vinfo) == vect_reduction_def
555 relevant = vect_used_in_outer_by_reduction;
559 relevant = vect_used_in_outer;
584 vect_mark_relevant (worklist, dstmt_vinfo, relevant, false);
615 enum vect_relevant relevant;
629 dump_printf_loc (MSG_NOTE, vect_location, "init: phi relevant? %G",
632 if (vect_stmt_relevant_p (phi_info, loop_vinfo, &relevant, &live_p))
633 vect_mark_relevant (&worklist, phi_info, relevant, live_p);
640 "init: stmt relevant? %G", stmt_info->stmt);
642 if (vect_stmt_relevant_p (stmt_info, loop_vinfo, &relevant, &live_p))
643 vect_mark_relevant (&worklist, stmt_info, relevant, live_p);
659 (DEF_STMT) as relevant/irrelevant according to the relevance property
661 relevant = STMT_VINFO_RELEVANT (stmt_vinfo);
668 This is because we distinguish between two kinds of relevant stmts -
677 gcc_assert (relevant != vect_unused_in_scope);
678 if (relevant != vect_unused_in_scope
679 && relevant != vect_used_in_scope
680 && relevant != vect_used_by_reduction
681 && relevant != vect_used_only_live)
687 if (relevant != vect_unused_in_scope
688 && relevant != vect_used_in_outer_by_reduction
689 && relevant != vect_used_in_outer)
695 if (relevant != vect_unused_in_scope
696 && relevant != vect_used_by_reduction
697 && relevant != vect_used_only_live)
721 loop_vinfo, relevant, &worklist, false);
725 loop_vinfo, relevant, &worklist, false);
736 = process_use (stmt_vinfo, op, loop_vinfo, relevant,
749 = process_use (stmt_vinfo, arg, loop_vinfo, relevant,
761 = process_use (stmt_vinfo, op, loop_vinfo, relevant,
773 = process_use (stmt_vinfo, gs_info.offset, loop_vinfo, relevant,
1575 STMT_VINFO_VEC_STMT of the defining stmt holds the relevant def.
1658 get the relevant vector-def for each operand of S2. For operand x it
1662 function is called to get the relevant vector-def for each operand. It is
6287 To vectorize stmt S2 we first need to find the relevant vector
6291 relevant vector def 'vx0'. Having found 'vx0' we can generate
6294 When creating the second copy (VS2_1), we obtain the relevant vector
6296 stmt VS1_0. This way we find the stmt VS1_1 and the relevant
10852 instance, therefore, all the statements are relevant.
10855 if the original statement is not relevant. Otherwise, we analyze both
10993 " relevant stmt not supported: %G",
11163 /* Find the relevant loop-exit phi-node, and reord the vec_stmt there