From: Jakub Jelinek <jakub@redhat.com>
To: Jan Hubicka <hubicka@ucw.cz>
Cc: gcc-patches@gcc.gnu.org, rguenther@suse.de
Subject: Re: Disable iteration in early inliner
Date: Wed, 23 Jan 2013 10:29:00 -0000 [thread overview]
Message-ID: <20130123102844.GC7269@tucnak.redhat.com> (raw)
In-Reply-To: <20130123101831.GA24040@kam.mff.cuni.cz>
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.
Jakub
next prev parent reply other threads:[~2013-01-23 10:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 10:18 Jan Hubicka
2013-01-23 10:29 ` Jakub Jelinek [this message]
2013-01-23 13:15 ` Jan Hubicka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130123102844.GC7269@tucnak.redhat.com \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=rguenther@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).