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: Disable iteration in early inliner

From: Jan Hubicka <hubicka at ucw dot cz>
To: Jakub Jelinek <jakub at redhat dot com>
Cc: Jan Hubicka <hubicka at ucw dot cz>, gcc-patches at gcc dot gnu dot org, rguenther at suse dot de
Date: Wed, 23 Jan 2013 14:14:49 +0100
Subject: Re: Disable iteration in early inliner
References: <20130123101831.GA24040@kam.mff.cuni.cz> <20130123102844.GC7269@tucnak.redhat.com>

> On Wed, Jan 23, 2013 at 11:18:31AM +0100, Jan Hubicka wrote:
> > Bootstrapped/regtested x86_64-linux, compensated the 3 testcases in tesuite testing
> > the feature to both test the feature with parameter increased and thest that the
> > optimization happens anyway at IPA level by default.
> 
> Not objecting to the patch, just wondering, if the fix is only about
> changing a default of a param, won't the PR55797 testcase still ICE
> if (to the -O -fno-guess-branch-probability -fno-tree-forwprop --param=early-inlining-insns=176
> options) one also adds --param=max-early-inliner-iterations=2 ?
> With --param=max-early-inliner-iterations=1 it indeed no longer ICEs.

It is not meant to be complette fix for PR55797, only the code quality issue Richi observed while
debugging it.  I am looking into the ICE now, too.  

Honza

References:
- Disable iteration in early inliner
  - From: Jan Hubicka
- Re: Disable iteration in early inliner
  - From: Jakub Jelinek

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