From: Jan Hubicka <hubicka@ucw.cz>
To: Richard Biener <richard.guenther@gmail.com>
Cc: Jakub Jelinek <jakub@redhat.com>, GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: Check that there are no missing probabilities
Date: Tue, 17 Oct 2017 12:18:00 -0000 [thread overview]
Message-ID: <20171017120908.GB94155@kam.mff.cuni.cz> (raw)
In-Reply-To: <CAFiYyc0Tg6vKkKhDq2h7f=xH-j93xyUSgNgvF7jq0GrGXmPgZQ@mail.gmail.com>
>
> graphite does
>
> if (changed)
> {
> cleanup_tree_cfg ();
> profile_status_for_fn (cfun) = PROFILE_ABSENT;
> release_recorded_exits (cfun);
> tree_estimate_probability (false);
>
> so it runs into CFG cleanup running before it properly resets counts.
>
> I wonder if we shouldn't simply get rid of the explicit checking calls in
> cfg cleanup... or if the profile checking should happen somewhere
> else.
>
> I'd also appreciate a better way for doing the above. Shouldn't we
> end up with a proper initialization on all edges as we just split
> existing ones and use create_empty_if_region_on_edge and
> create_empty_loop_on_edge?
>
> Ah, those use make_edge as well.
>
> The tree_estimate_probablility call above should be ideally
> replaced with sth like "propagate-SESE-entry-probability".
Well, re-running tree_estimate_probability is a hack and it won't
really get you very sane profile update. I gues create_empty_if_region_on_edge
and create_empty_loop_on_edge should care about profile, i will try to take
a look.
We have frequency propagation across SEME regions as part of find_sub_basic_blocks.
It does not handle loops sanely though (which could be added), but still someone
needs to care about correct probabilities at least.
Honza
>
> Richard.
>
> > Jakub
next prev parent reply other threads:[~2017-10-17 12:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-13 14:04 Jan Hubicka
2017-10-13 17:13 ` Jakub Jelinek
2017-10-13 19:14 ` Jan Hubicka
2017-10-13 19:30 ` Jakub Jelinek
2017-10-13 19:37 ` Jan Hubicka
2017-10-17 11:45 ` Richard Biener
2017-10-17 12:18 ` Jan Hubicka [this message]
2017-10-13 20:56 ` Andrew Pinski
2017-10-13 19:07 David Edelsohn
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=20171017120908.GB94155@kam.mff.cuni.cz \
--to=hubicka@ucw.cz \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=richard.guenther@gmail.com \
/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).