On Thu, Jun 6, 2013 at 1:33 PM, Xinliang David Li wrote:
> ok. Wht is the rational for dropping the limit in trunk? Ideally,
> the limit should be lifted up and to enable other heuristics to kick
> in.
Here is the message about it from Honza:
http://gcc.gnu.org/ml/gcc-patches/2012-11/msg01193
ok. Wht is the rational for dropping the limit in trunk? Ideally,
the limit should be lifted up and to enable other heuristics to kick
in.
David
On Thu, Jun 6, 2013 at 1:22 PM, Teresa Johnson wrote:
> The default for the max instructions in peeled loops was reduced on
> trunk in r193570. This
We should make the default setting right for our environment. The
patch is trivial to maintain.
thanks,
David
On Thu, Jun 6, 2013 at 1:26 PM, Diego Novillo wrote:
> On 2013-06-06 16:22 , Teresa Johnson wrote:
>>
>> The default for the max instructions in peeled loops was reduced on
>> trunk in
On 2013-06-06 16:22 , Teresa Johnson wrote:
The default for the max instructions in peeled loops was reduced on
trunk in r193570. This is causing a performance regression on an internal
benchmark. This change will revert to the old higher limits.
Google ref b/8839137.
Bootstrapped and tested. O
The default for the max instructions in peeled loops was reduced on
trunk in r193570. This is causing a performance regression on an internal
benchmark. This change will revert to the old higher limits.
Google ref b/8839137.
Bootstrapped and tested. Ok for google/4_8?
Thanks,
Teresa
2013-06-06
