tree-vect-loop.c (vect_analyze_loop_2): Use likely_max_stmt_executions_int.

	* tree-vect-loop.c (vect_analyze_loop_2): Use
	likely_max_stmt_executions_int.

From-SVN: r236870

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 3aa51c9ffa53a0f34927c60460108ae874694c67..4617eb60d6ce30a03ab07c0099c9d434e48f6a44 100644 (file)
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,8 @@
+2016-05-30  Jan Hubicka  <hubicka@ucw.cz>
+
+       * tree-vect-loop.c (vect_analyze_loop_2): Use
+       likely_max_stmt_executions_int.
+
 2016-05-30  Tom de Vries  <tom@codesourcery.com>
 
        PR tree-optimization/69067

diff --git a/gcc/tree-vect-loop.c b/gcc/tree-vect-loop.c
index 1471658da763d5f58df95023d0168f97b00fd5f3..cada09692fb8ec8160b3949d6e4bc4d5a4b7965c 100644 (file)
--- a/gcc/tree-vect-loop.c
+++ b/gcc/tree-vect-loop.c
@@ -1945,7 +1945,7 @@ start_over:
                     LOOP_VINFO_INT_NITERS (loop_vinfo));
 
   HOST_WIDE_INT max_niter
-    = max_stmt_executions_int (LOOP_VINFO_LOOP (loop_vinfo));
+    = likely_max_stmt_executions_int (LOOP_VINFO_LOOP (loop_vinfo));
   if ((LOOP_VINFO_NITERS_KNOWN_P (loop_vinfo)
        && (LOOP_VINFO_INT_NITERS (loop_vinfo) < vectorization_factor))
       || (max_niter != -1