public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/40436] [4.5 regression] 0.5% code size regression caused by r147852
Date: Sat, 03 Apr 2010 21:13:00 -0000 [thread overview]
Message-ID: <20100403211325.25590.qmail@sourceware.org> (raw)
In-Reply-To: <bug-40436-374@http.gcc.gnu.org/bugzilla/>
------- Comment #24 from rguenther at suse dot de 2010-04-03 21:13 -------
Subject: Re: [4.5 regression] 0.5% code size
regression caused by r147852
On Sat, 3 Apr 2010, hubicka at ucw dot cz wrote:
> ------- Comment #23 from hubicka at ucw dot cz 2010-04-03 21:02 -------
> Subject: Re: [4.5 regression] 0.5% code size
> regression caused by r147852
>
> > 1) overall_size is reduced twice for the same function, once in
> > cgraph_clone_inlined_nodes, once in cgraph_mark_inline_edge (which calls
> > the former), this leads to double accounting
>
> Hmm, yep, it is bug here and I guess it makes tramp3d unhappy since it relies
> on
> the overall unit growth. I will try to fix this and retune to see if this can
> be
> used to help the CSiBE regression that also might be related to this thinko.
>
> > 2) cgraph_check_inline_limits checks the wrong size against the
> > PARAM_LARGE_FUNCTION_INSNS parameter, it needs to use the original size,
> > not the one estimated after inlining.
> Well, PARAM_LARGE_FUNCTION_INSNS was meant to let small functions to grow as
> much
> as they want until the threshold is hit, so size after inlining makes sense
> here.
But the the code as-is allows unlimited growth of a function (well,
by PARAM_LARGE_FUNCTION_GROWTH for each inlining; the limit is
basically PARAM_LARGE_FUNCTION_INSNS * (1 +
PARAM_LARGE_FUNCTION_GROWTH/100) ^ n with n being the number of
functions we inline into the function). So it's not really a
limit of the growth but of the growth rate ;)
Richard.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40436
next prev parent reply other threads:[~2010-04-03 21:13 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-13 22:35 [Bug tree-optimization/40436] New: " rearnsha at gcc dot gnu dot org
2009-06-13 22:51 ` [Bug tree-optimization/40436] " rguenth at gcc dot gnu dot org
2009-06-13 22:53 ` rguenth at gcc dot gnu dot org
2009-06-13 23:07 ` pinskia at gcc dot gnu dot org
2009-06-13 23:10 ` rearnsha at gcc dot gnu dot org
2009-06-13 23:27 ` rearnsha at gcc dot gnu dot org
2009-06-14 13:31 ` rguenth at gcc dot gnu dot org
2009-06-19 0:00 ` ramana at gcc dot gnu dot org
2009-06-19 23:14 ` ramana at gcc dot gnu dot org
2009-06-30 12:44 ` hubicka at gcc dot gnu dot org
2009-06-30 12:46 ` hubicka at ucw dot cz
2009-06-30 13:14 ` steven at gcc dot gnu dot org
2009-06-30 13:41 ` hubicka at gcc dot gnu dot org
2009-06-30 19:56 ` steven at gcc dot gnu dot org
2009-06-30 23:37 ` hubicka at ucw dot cz
2009-07-01 5:41 ` steven at gcc dot gnu dot org
2009-07-02 10:11 ` hubicka at ucw dot cz
2009-07-09 15:39 ` rguenth at gcc dot gnu dot org
2009-12-09 17:09 ` ramana at gcc dot gnu dot org
2010-03-07 20:37 ` hubicka at gcc dot gnu dot org
2010-03-28 15:47 ` rguenth at gcc dot gnu dot org
2010-03-28 16:34 ` hubicka at ucw dot cz
2010-03-28 16:43 ` rguenther at suse dot de
2010-03-28 16:56 ` hubicka at ucw dot cz
2010-03-28 17:00 ` rguenther at suse dot de
2010-03-28 17:30 ` hubicka at ucw dot cz
2010-04-03 21:02 ` hubicka at ucw dot cz
2010-04-03 21:13 ` rguenther at suse dot de [this message]
2010-04-03 21:19 ` hubicka at ucw dot cz
2010-04-03 21:21 ` hubicka at ucw dot cz
2010-04-03 21:39 ` hubicka at ucw dot cz
2010-04-06 10:36 ` matz at gcc dot gnu dot org
2010-04-06 10:46 ` hubicka at ucw dot cz
2010-04-06 10:57 ` steven at gcc dot gnu dot org
2010-04-06 11:00 ` rguenther at suse dot de
2010-04-06 11:05 ` hubicka at ucw dot cz
2010-04-06 11:10 ` matz at gcc dot gnu dot org
2010-04-06 11:37 ` steven at gcc dot gnu dot org
2010-04-06 11:39 ` rguenth at gcc dot gnu dot org
2010-07-31 9:35 ` [Bug tree-optimization/40436] [4.5/4.6 " rguenth at gcc dot gnu dot org
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=20100403211325.25590.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).