public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Martin Liška" <mliska@suse.cz>
To: Aditya K <hiraditya@msn.com>, "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Cc: Jan Hubicka <hubicka@ucw.cz>
Subject: Re: GSoC topic: Implement hot cold splitting at GIMPLE IR level
Date: Tue, 03 Mar 2020 08:47:00 -0000	[thread overview]
Message-ID: <453b83f8-4422-7727-ddd9-5f9e0d23d873@suse.cz> (raw)
In-Reply-To: <BYAPR08MB4232069B0A9D5D1E0E4B2A69B6E40@BYAPR08MB4232.namprd08.prod.outlook.com>

Hello.

Thank you for idea. I would like to provide some comments about what GCC can currently
do and I'm curious we need something extra on top of what we do.
Right now, GCC can do hot/cold partitioning based on functions and basic blocks. With
a PGO profile, the optimization is quite aggressive and can save quite some code
being placed into a cold partitioning and being optimized for size. Without a profile,
we do a static profile guess (predict.c), where we also propagate information about cold
blocks (determine_unlikely_bbs). Later in RTL, we utilize the information and make
the real reordering (bb-reorder.c).

Martin

  reply	other threads:[~2020-03-03  8:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-03  5:51 Aditya K
2020-03-03  8:47 ` Martin Liška [this message]
     [not found]   ` <BYAPR08MB42320E829A37607C0AC4F967B6E40@BYAPR08MB4232.namprd08.prod.outlook.com>
2020-03-03 20:42     ` Fw: " Aditya K
2020-03-03 21:25       ` Jan Hubicka
2020-03-05 15:50         ` Segher Boessenkool
2020-03-16 23:11         ` Aditya K
2020-03-16 23:19           ` Jakub Jelinek
2020-03-17 14:31             ` Aditya K
2020-03-17 14:47               ` Richard Biener

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=453b83f8-4422-7727-ddd9-5f9e0d23d873@suse.cz \
    --to=mliska@suse.cz \
    --cc=gcc@gcc.gnu.org \
    --cc=hiraditya@msn.com \
    --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).