FreeChainXenon/gcc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

vect: Tweak dump messages for vector mode choice

Browse source 
After vect_analyze_loop has successfully analysed a loop for
one base vector mode B1, it considers using following base vector
modes to vectorise an epilogue.  However, for VECT_COMPARE_COSTS,
a later mode B2 might turn out to be better than B1 was.  Initially
this comparison will be between an epilogue loop (for B2) and a main
loop (for B1).  However, in r11-6458 I'd added code to reanalyse the
B2 epilogue loop as a main loop, partly for correctness and partly
for better costing.

This can lead to a situation in which we think that the B2 epilogue
loop was better than the B1 main loop, but that the B2 main loop is
not better than the B1 main loop.  There was no dump message to say
that this had happened, which made it look like B2 had still won.

gcc/
	* tree-vect-loop.c (vect_analyze_loop): Print a dump message
	when a reanalyzed loop fails to be cheaper than the current
	main loop.
This commit is contained in:
Richard Sandiford 2021-08-04 16:52:08 +01:00
parent eb55b5b0df
commit 315a1c3756
1 changed files with 10 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
gcc/tree-vect-loop.c
View file

@ -3064,7 +3064,16 @@ vect_analyze_loop (class loop *loop, vec_info_shared *shared)
= opt_loop_vec_info::success (main_loop_vinfo);
}
else
delete main_loop_vinfo;
{
if (dump_enabled_p ())
dump_printf_loc (MSG_NOTE, vect_location,
"***** No longer preferring vector"
" mode %s after reanalyzing the loop"
" as a main loop\n",
GET_MODE_NAME
(main_loop_vinfo->vector_mode));
delete main_loop_vinfo;
}
}
}