public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/65076] [5 Regression] 16% tramp3d-v4.cpp compile time regression Date: Sat, 28 Mar 2015 22:17:00 -0000 [thread overview] Message-ID: <bug-65076-4-3Agozq1sLQ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65076-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65076 --- Comment #27 from Jan Hubicka <hubicka at gcc dot gnu.org> --- Unfortunately from me it wend down from about 18% to 15%, so still a regression. One quantiative parameter I can measure is increase of number of functions in the resulting binary from 1030 to 1140. I will try to double check if that is bug of unreachable code removal or a property of new inliner metrics preferring fewer full inlines.
next prev parent reply other threads:[~2015-03-28 19:33 UTC|newest] Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-02-16 13:00 [Bug ipa/65076] New: " trippels at gcc dot gnu.org 2015-02-16 13:14 ` [Bug ipa/65076] " rguenth at gcc dot gnu.org 2015-02-16 13:22 ` trippels at gcc dot gnu.org 2015-02-16 18:31 ` hubicka at gcc dot gnu.org 2015-02-16 19:07 ` trippels at gcc dot gnu.org 2015-02-16 19:15 ` trippels at gcc dot gnu.org 2015-02-17 10:49 ` rguenth at gcc dot gnu.org 2015-03-04 9:10 ` rguenth at gcc dot gnu.org 2015-03-18 12:56 ` rguenth at gcc dot gnu.org 2015-03-21 5:32 ` hubicka at gcc dot gnu.org 2015-03-21 10:25 ` hubicka at gcc dot gnu.org 2015-03-21 10:48 ` hubicka at gcc dot gnu.org 2015-03-21 11:32 ` hubicka at gcc dot gnu.org 2015-03-24 14:56 ` rguenth at gcc dot gnu.org 2015-03-24 17:21 ` jakub at gcc dot gnu.org 2015-03-25 8:42 ` hubicka at gcc dot gnu.org 2015-03-25 8:42 ` hubicka at ucw dot cz 2015-03-25 8:50 ` rguenther at suse dot de 2015-03-25 21:35 ` hubicka at gcc dot gnu.org 2015-03-26 3:23 ` hubicka at gcc dot gnu.org 2015-03-27 4:03 ` hubicka at gcc dot gnu.org 2015-03-27 6:21 ` hubicka at gcc dot gnu.org 2015-03-27 9:34 ` rguenth at gcc dot gnu.org 2015-03-28 22:17 ` hubicka at gcc dot gnu.org [this message] 2015-03-29 14:29 ` trippels at gcc dot gnu.org 2015-03-30 6:03 ` hubicka at gcc dot gnu.org 2015-03-30 6:15 ` hubicka at gcc dot gnu.org 2015-03-31 13:03 ` rguenth at gcc dot gnu.org 2015-03-31 13:09 ` trippels at gcc dot gnu.org 2015-03-31 14:10 ` rguenther at suse dot de 2015-03-31 14:13 ` trippels at gcc dot gnu.org 2015-03-31 14:47 ` trippels at gcc dot gnu.org 2015-03-31 15:08 ` trippels at gcc dot gnu.org 2015-03-31 15:10 ` evstupac at gmail dot com 2015-03-31 15:29 ` rguenth at gcc dot gnu.org 2015-03-31 16:06 ` hubicka at ucw dot cz 2015-03-31 16:25 ` hubicka at gcc dot gnu.org 2015-03-31 17:36 ` hubicka at gcc dot gnu.org 2015-03-31 17:53 ` hubicka at gcc dot gnu.org 2015-03-31 17:54 ` hubicka at gcc dot gnu.org 2015-03-31 20:31 ` trippels at gcc dot gnu.org 2015-04-01 8:02 ` rguenther at suse dot de 2015-04-01 8:05 ` rguenther at suse dot de 2015-04-01 8:28 ` hubicka at gcc dot gnu.org 2015-04-01 8:34 ` trippels at gcc dot gnu.org 2015-04-02 5:18 ` hubicka at gcc dot gnu.org 2015-04-02 7:07 ` hubicka at gcc dot gnu.org 2015-04-02 23:44 ` hubicka at gcc dot gnu.org 2015-04-03 18:09 ` hubicka at gcc dot gnu.org 2015-04-07 9:32 ` rguenth at gcc dot gnu.org 2015-04-22 1:32 ` [Bug ipa/65076] [5/6 " hubicka at gcc dot gnu.org 2015-04-22 12:06 ` jakub at gcc dot gnu.org 2015-07-16 9:19 ` rguenth at gcc dot gnu.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=bug-65076-4-3Agozq1sLQ@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).