* [PATCH GCC]Obvious change, dump min_profitable_estimate, rather than min_profitable_iters
@ 2016-02-22 11:11 Bin Cheng
2016-02-22 13:47 ` Richard Biener
0 siblings, 1 reply; 2+ messages in thread
From: Bin Cheng @ 2016-02-22 11:11 UTC (permalink / raw)
To: gcc-patches; +Cc: nd
[-- Attachment #1: Type: text/plain, Size: 537 bytes --]
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.
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.
[-- Attachment #2: dump-typo-min_profitable_estimate-20160219.txt --]
[-- Type: text/plain, Size: 684 bytes --]
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;
}
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [PATCH GCC]Obvious change, dump min_profitable_estimate, rather than min_profitable_iters
2016-02-22 11:11 [PATCH GCC]Obvious change, dump min_profitable_estimate, rather than min_profitable_iters Bin Cheng
@ 2016-02-22 13:47 ` Richard Biener
0 siblings, 0 replies; 2+ messages in thread
From: Richard Biener @ 2016-02-22 13:47 UTC (permalink / raw)
To: Bin Cheng; +Cc: gcc-patches, nd
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2016-02-22 13:47 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-02-22 11:11 [PATCH GCC]Obvious change, dump min_profitable_estimate, rather than min_profitable_iters Bin Cheng
2016-02-22 13:47 ` Richard Biener
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).