From: "H.J. Lu" <hjl.tools@gmail.com>
To: Jan Hubicka <hubicka@ucw.cz>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
David Edelsohn <dje.gcc@gmail.com>
Subject: Re: Make cgraph frequencies more precise
Date: Mon, 12 Oct 2015 15:08:00 -0000 [thread overview]
Message-ID: <CAMe9rOrixioyW6CG8WJhGpdv3pPoUVTS7FnU1Rtjk7U7yOUh+Q@mail.gmail.com> (raw)
In-Reply-To: <20151012060727.GB53108@kam.mff.cuni.cz>
On Sun, Oct 11, 2015 at 11:07 PM, Jan Hubicka <hubicka@ucw.cz> wrote:
> Hi,
> this patch fixes a case of extreme imprecision I noticed while looking into
> profiles of PHP interpretter. There is a function that is called 22 times
> and contains the main loop. Now since the frequency of entry block is dropped
> to 0, we do not have any information of relative frequencies in the colder
> areas of the function.
>
> Hope all this uglyness with go away with conversion to sreals soonish.
>
> Profiledbootstrapped/regtested ppc64le-linux, comitted.
> * cgraphbuild.c (compute_call_stmt_bb_frequency): Use
> counts when these are more informative.
This caused:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67931
--
H.J.
next prev parent reply other threads:[~2015-10-12 15:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-12 6:07 Jan Hubicka
2015-10-12 15:08 ` H.J. Lu [this message]
2015-10-12 18:53 ` Jan Hubicka
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=CAMe9rOrixioyW6CG8WJhGpdv3pPoUVTS7FnU1Rtjk7U7yOUh+Q@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
/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).