| Message ID | HE1PR08MB0507955EB65D10561467D075E7A30@HE1PR08MB0507.eurprd08.prod.outlook.com |
|---|---|
| State | New |
| Headers | show |
On Mon, Feb 22, 2016 at 12:10 PM, Bin Cheng <Bin.Cheng@arm.com> wrote: > Hi, > This is an obvious change to vect_estimate_min_profitable_iters. Given the context, it should dump min_profitable_estimate at patch site, rather than min_profitable_iters. Or I must mis-understood something in the code. > Build successfully, no test needed. Is it OK? I am not sure obvious change rule can be applied during stage4 or not. Ok to commit. RIchard. > Thanks, > bin > > 2016-02-22 Bin Cheng <bin.cheng@arm.com> > > * tree-vect-loop.c (vect_estimate_min_profitable_iters): Dump > min_profitable_estimate, rather than min_profitable_iters.
Index: gcc/tree-vect-loop.c =================================================================== --- gcc/tree-vect-loop.c (revision 233556) +++ gcc/tree-vect-loop.c (working copy) @@ -3430,8 +3430,8 @@ vect_estimate_min_profitable_iters (loop_vec_info min_profitable_estimate = MAX (min_profitable_estimate, min_profitable_iters); if (dump_enabled_p ()) dump_printf_loc (MSG_NOTE, vect_location, - " Static estimate profitability threshold = %d\n", - min_profitable_iters); + " Static estimate profitability threshold = %d\n", + min_profitable_estimate); *ret_min_profitable_estimate = min_profitable_estimate; }