public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "markus at trippelsdorf dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/55674] [4.8 Regression] >20%  size increase of lto/pgo binaries since r193747
Date: Thu, 13 Dec 2012 22:35:00 -0000	[thread overview]
Message-ID: <bug-55674-4-xO5SbdO9cR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55674-4@http.gcc.gnu.org/bugzilla/>


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55674

--- Comment #12 from Markus Trippelsdorf <markus at trippelsdorf dot de> 2012-12-13 22:35:33 UTC ---
(In reply to comment #11)
> Do you happen to know what it was with lto/pgo before the change? Should be
> roughly equivalent to hot-bb-count-ws-permille=970 from what I saw in your
> profiles

Yes, it was ~34MB before the change.

> What size increase is acceptable?

It's hard to say in case of Firefox, because the only thing
that one can reliably measure is the JavaScript performance.
And this varies only very slightly with different compiler options.
So you have no way to measure up to which point more inlining
is still beneficial.


  parent reply	other threads:[~2012-12-13 22:35 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-13 12:56 [Bug gcov-profile/55674] New: " markus at trippelsdorf dot de
2012-12-13 13:29 ` [Bug gcov-profile/55674] " rguenth at gcc dot gnu.org
2012-12-13 14:45 ` tejohnson at google dot com
2012-12-13 14:46 ` markus at trippelsdorf dot de
2012-12-13 14:49 ` tejohnson at google dot com
2012-12-13 14:53 ` markus at trippelsdorf dot de
2012-12-13 15:03 ` tejohnson at google dot com
2012-12-13 15:06 ` markus at trippelsdorf dot de
2012-12-13 15:50 ` tejohnson at google dot com
2012-12-13 18:23 ` tejohnson at google dot com
2012-12-13 19:11 ` markus at trippelsdorf dot de
2012-12-13 22:14 ` markus at trippelsdorf dot de
2012-12-13 22:16 ` tejohnson at google dot com
2012-12-13 22:35 ` markus at trippelsdorf dot de [this message]
2012-12-14 15:11 ` tejohnson at gcc dot gnu.org
2012-12-14 16:31 ` markus at trippelsdorf dot de
2012-12-18 15:41 ` hubicka at ucw dot cz
2012-12-18 17:04 ` markus at trippelsdorf dot de
2012-12-18 17:25 ` hubicka at ucw dot cz
2012-12-19 16:45 ` tejohnson at google dot com
2012-12-21 16:16 ` hubicka at ucw dot cz
2012-12-21 16:26 ` tejohnson at google dot com
2012-12-22 23:20 ` hubicka at ucw dot cz
2013-01-11 18:19 ` tejohnson at google dot com

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=bug-55674-4-xO5SbdO9cR@http.gcc.gnu.org/bugzilla/ \
    --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).