Ok for google/main.
1) may be better to omit the const iteration count for complete unroll message
2) Instead of dumping loop header count, is it better to dump
pre-header count -- it gives an idea of how often the loop is entered.
The loop header count can be derived from loop average iteration a
On Tue, Nov 1, 2011 at 2:53 AM, Richard Guenther
wrote:
> On Tue, Nov 1, 2011 at 1:46 AM, Teresa Johnson wrote:
>> This patch is for google-main only.
>>
>> Tested with bootstrap and regression tests.
>>
>> Print unroll and peel factors along with loop source position under
>> -fopt-info.
>>
>>
Hi Richard,
Once we have a uniform way to emit notes to either stderr or dump, as
you and David had discussed in the earlier thread, we can merge these
two messages. The advantage with the new messages, besides going to
stderr, is that the source position information is being emitted since
it is a
On Tue, Nov 1, 2011 at 1:46 AM, Teresa Johnson wrote:
> This patch is for google-main only.
>
> Tested with bootstrap and regression tests.
>
> Print unroll and peel factors along with loop source position under
> -fopt-info.
>
> Teresa
>
> 2011-10-31 Teresa Johnson
>
> * common.opt (f
