From: Jan Hubicka <hubicka@ucw.cz>
To: Jeff Law <law@redhat.com>
Cc: Jan Hubicka <hubicka@ucw.cz>, gcc-patches@gcc.gnu.org, rguenther@suse.de
Subject: Re: Early jump threading
Date: Tue, 16 Aug 2016 11:02:00 -0000 [thread overview]
Message-ID: <20160816110252.GB26405@kam.mff.cuni.cz> (raw)
In-Reply-To: <b6b52fed-e234-e48b-6815-1c4f62e6c103@redhat.com>
> I don't think the backwards/FSM threader tries to update the profile
> data at all right now.
This seems to be cause of the regression andrew is speaking about. I wrote updating
of profile after threading few times and there was also Theresa's patch.
I tought all the threaders use common duplication engine and that one does the updating?
I will try to dive into the code, but creating basic blocks with frequency 0 across hot
paths is bad idea - they will be optimized for size.
Honza
next prev parent reply other threads:[~2016-08-16 11:02 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-11 14:02 Jan Hubicka
2016-08-11 14:06 ` Richard Biener
2016-08-11 14:27 ` Jan Hubicka
2016-08-11 15:50 ` Richard Biener
2016-08-11 18:42 ` Jeff Law
2016-09-18 19:30 ` Jan Hubicka
2016-09-19 6:53 ` Andrew Pinski
2016-09-19 9:29 ` Jan Hubicka
2016-10-18 15:56 ` James Greenhalgh
2016-12-15 11:54 ` [Patch] Undermine the jump threading cost model to fix PR77445 James Greenhalgh
2016-12-16 12:34 ` Richard Biener
2016-09-19 7:59 ` Early jump threading Christophe Lyon
2016-09-20 8:41 ` Thomas Preudhomme
2016-08-11 18:41 ` Jeff Law
2016-08-12 6:02 ` Richard Biener
2016-08-15 17:06 ` Jeff Law
2016-08-11 18:30 ` Jeff Law
2016-08-11 18:29 ` Jeff Law
2016-08-16 11:02 ` Jan Hubicka [this message]
2016-08-16 15:42 ` Jeff Law
2016-08-12 8:02 ` Richard Biener
2016-08-12 11:27 ` Jan Hubicka
2016-08-15 17:25 ` Jeff Law
2016-08-16 16:52 ` Jeff Law
2016-08-18 19:55 ` Jeff Law
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=20160816110252.GB26405@kam.mff.cuni.cz \
--to=hubicka@ucw.cz \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@redhat.com \
--cc=rguenther@suse.de \
/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).