From: Aditya K <hiraditya@msn.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Jan Hubicka <hubicka@ucw.cz>, "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Fw: GSoC topic: Implement hot cold splitting at GIMPLE IR level
Date: Tue, 17 Mar 2020 14:31:51 +0000 [thread overview]
Message-ID: <BYAPR08MB4232C5A14BC98BA564D691FEB6F60@BYAPR08MB4232.namprd08.prod.outlook.com> (raw)
In-Reply-To: <20200316231916.GT2156@tucnak>
As I understand the openmp outliner is also at the tree level. A region based outliner could be reused there. I’m not particular about the outliner being specific to ipa-split. A GSoC project can help us get the coding+testing done. Any pass that needs a function splitting at tree level can reuse them.
-Aditya
________________________________
From: Jakub Jelinek <jakub@redhat.com>
Sent: Monday, March 16, 2020 5:19:16 PM
To: Aditya K <hiraditya@msn.com>
Cc: Jan Hubicka <hubicka@ucw.cz>; gcc@gcc.gnu.org <gcc@gcc.gnu.org>
Subject: Re: Fw: GSoC topic: Implement hot cold splitting at GIMPLE IR level
On Mon, Mar 16, 2020 at 11:11:14PM +0000, Aditya K via Gcc wrote:
> >
> > 2) ipa-split is very simplistic and only splits when there is no value
> > computed in header of function used in the tail. We should support
> > adding extra parameters for values computed and do more general SESE
> > outlining
> > Note that we do SESE outlining for openMP but this code is not
> > interfaced very generically to be easilly used by ipa-split.
>
> This sounds like a good GSoC project to work on. We could have a SESE/SEME based ipa-split, that
> could help with function splitting as well as openMP.
No, OpenMP region outlining needs to be done where it is done currently,
ipa-split is way too late for that.
Jakub
next prev parent reply other threads:[~2020-03-17 14:31 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
[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 [this message]
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=BYAPR08MB4232C5A14BC98BA564D691FEB6F60@BYAPR08MB4232.namprd08.prod.outlook.com \
--to=hiraditya@msn.com \
--cc=gcc@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=jakub@redhat.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).