public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tejohnson at google dot com" <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: Wed, 19 Dec 2012 16:45:00 -0000 [thread overview] Message-ID: <bug-55674-4-NnV8L7VpRI@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 #18 from Teresa Johnson <tejohnson at google dot com> 2012-12-19 16:44:21 UTC --- On Tue, Dec 18, 2012 at 9:25 AM, hubicka at ucw dot cz <gcc-bugzilla@gcc.gnu.org> wrote: > > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55674 > > --- Comment #17 from Jan Hubicka <hubicka at ucw dot cz> 2012-12-18 17:25:37 UTC --- >> I did some measurements with tramp3d and in this case >> the default (999) gives the best performance: >> >> par. size time >> -------------------- >> 999 955859 3.71752 >> 990 933390 3.73969 >> 980 904718 3.84547 >> ... " " >> 750 904718 3.84769 >> 740 837654 7.67177 >> 600 836024 8.80879 > > Yep, tramp3d is unforutnately quite special case: we measure the number of > instructions prior > late optimization, while in tramp3d over 90% of code disappear as a result of > inlining and further > simplification, so we get GIGO problem... > > I am not sure how to handle these things in any resonable way.... > > I will test couple of values on spec2k this week and lets see how things scale > elsewhere. As another data point, in our internal benchmarks I had tried a few values and 99.9% gave the best performance. Just going down to 99.0% reduced the inlining too much, even compared to the old static cutoff count, missing some key inlines and reducing performance. Thanks, Teresa > > Honza > > -- > Configure bugmail: http://gcc.gnu.org/bugzilla/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You are on the CC list for the bug. -- Teresa Johnson | Software Engineer | tejohnson@google.com | 408-460-2413
next prev parent reply other threads:[~2012-12-19 16:45 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 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 [this message] 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-NnV8L7VpRI@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: linkBe 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).