This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [google gcc-4_8] Restore max peeled instructions to old default

From: Diego Novillo <dnovillo at google dot com>
To: Teresa Johnson <tejohnson at google dot com>
Cc: "gcc-patches at gcc dot gnu dot org" <gcc-patches at gcc dot gnu dot org>, David Li <davidxl at google dot com>
Date: Thu, 06 Jun 2013 16:26:04 -0400
Subject: Re: [google gcc-4_8] Restore max peeled instructions to old default
References: <CAAe5K+WiCh0vBSSb14UJMD=tjLpJCLdH2p_oup2Z7Q3C71HMnA at mail dot gmail dot com>

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. Ok for google/4_8?

I wonder if this isn't something we want to set in our internal buildconfiguration files. I don't have a strong opinion one way or theother, however. I'm only saying this because it would mean 1 less patchfor us to maintain.



Diego.

Follow-Ups:
- Re: [google gcc-4_8] Restore max peeled instructions to old default
  - From: Xinliang David Li

References:
- [google gcc-4_8] Restore max peeled instructions to old default
  - From: Teresa Johnson

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]