From 4b493b442641c3d5e07bf207b84df0f508345735 Mon Sep 17 00:00:00 2001 From: David Malcolm Date: Wed, 13 Jun 2018 15:28:17 -0400 Subject: [PATCH 20/46] tree-vect-loop.c: use MSG_OPTIMIZED_LOCATIONS in a few places I noticed when reviewing an HTML report generated from optimization records generated in turn from the existing API calls that we sometimes use MSG_NOTE when MSG_OPTIMIZED_LOCATIONS would be more appropriate (to denote a successful optimization). gcc/ChangeLog: * tree-vect-loop.c (vect_transform_loop): Use MSG_OPTIMIZED_LOCATIONS rather than MSG_NOTE when reporting on vectorized loops and epilogues. --- gcc/tree-vect-loop.c | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/gcc/tree-vect-loop.c b/gcc/tree-vect-loop.c index 67e8efe..acd1a8c 100644 --- a/gcc/tree-vect-loop.c +++ b/gcc/tree-vect-loop.c @@ -8688,19 +8688,19 @@ vect_transform_loop (loop_vec_info loop_vinfo) { if (!LOOP_VINFO_EPILOGUE_P (loop_vinfo)) { - dump_printf_loc (MSG_NOTE, vect_location, + dump_printf_loc (MSG_OPTIMIZED_LOCATIONS, vect_location, "LOOP VECTORIZED\n"); if (loop->inner) - dump_printf_loc (MSG_NOTE, vect_location, + dump_printf_loc (MSG_OPTIMIZED_LOCATIONS, vect_location, "OUTER LOOP VECTORIZED\n"); - dump_printf (MSG_NOTE, "\n"); + dump_printf (MSG_OPTIMIZED_LOCATIONS, "\n"); } else { - dump_printf_loc (MSG_NOTE, vect_location, + dump_printf_loc (MSG_OPTIMIZED_LOCATIONS, vect_location, "LOOP EPILOGUE VECTORIZED (VS="); - dump_dec (MSG_NOTE, current_vector_size); - dump_printf (MSG_NOTE, ")\n"); + dump_dec (MSG_OPTIMIZED_LOCATIONS, current_vector_size); + dump_printf (MSG_OPTIMIZED_LOCATIONS, ")\n"); } } -- 1.8.5.3