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/64425] [5 Regression] r219076 causes 36% tramp3d slowdown
Date: Mon, 12 Jan 2015 09:28:00 -0000	[thread overview]
Message-ID: <bug-64425-4-NGz6ukUmNR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64425-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64425

--- Comment #5 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
Author: hubicka
Date: Mon Jan 12 09:28:15 2015
New Revision: 219452

URL: https://gcc.gnu.org/viewcvs?rev=219452&root=gcc&view=rev
Log:

    PR ipa/63967
    PR ipa/64425
    * ipa-inline.c (compute_uninlined_call_time,
    compute_inlined_call_time): Use counts for extra precision when
    needed possible.
    (big_speedup_p): Fix formating.
    (RELATIVE_TIME_BENEFIT_RANGE): Remove.
    (relative_time_benefit): Remove.
    (edge_badness): Turn DECL_DISREGARD_INLINE_LIMITS into hint;
    merge guessed and read profile paths.
    (inline_small_functions): Count only !optimize_size functions into
    initial size; be more lax about sanity check when profile is used;
    be sure to update inlined function profile when profile is read.

Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/ipa-inline.c


  parent reply	other threads:[~2015-01-12  9:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-28  9:30 [Bug ipa/64425] New: " trippels at gcc dot gnu.org
2014-12-28  9:38 ` [Bug ipa/64425] " trippels at gcc dot gnu.org
2014-12-28 19:02 ` hjl.tools at gmail dot com
2015-01-04 16:37 ` hubicka at gcc dot gnu.org
2015-01-04 16:51 ` trippels at gcc dot gnu.org
2015-01-12  9:28 ` hubicka at gcc dot gnu.org [this message]
2015-01-12 10:18 ` trippels 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-64425-4-NGz6ukUmNR@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).