From: "Bin.Cheng" <amker.cheng@gmail.com>
To: marxin <mliska@suse.cz>
Cc: gcc-patches List <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 0/3] IVOPTS: support profiling
Date: Tue, 03 May 2016 09:28:00 -0000 [thread overview]
Message-ID: <CAHFci2_YrsL8k1sTR__Awa6SfV1-vC1fznc7rz_nUFcf7mDfWw@mail.gmail.com> (raw)
In-Reply-To: <cover.1461931011.git.mliska@suse.cz>
On Fri, Apr 29, 2016 at 12:56 PM, marxin <mliska@suse.cz> wrote:
> Hello.
>
> As profile-guided optimization can provide very useful information
> about basic block frequencies within a loop, following patch set leverages
> that information. It speeds up a single benchmark from upcoming SPECv6
> suite by 20% (-O2 -profile-generate/-fprofile use) and I think it can
> also improve others (currently measuring numbers for PGO).
>
> Idea is quite simple, where each cost (belonging to a BB) is
> multiplied by (bb_frequency / header_frequency), which suppress IV uses
> in basic blocks with a low frequency.
>
> The patch set can bootstrap on ppc64le-linux-gnu (and also
> x86_64-linux-gnu) and no new regression is introduced.
>
> Ready for trunk?
Hi Martin,
Thanks for working on this. I will first measure it on AArch64 and
read it in details.
Thanks,
bin
> Thanks,
> Martin
>
> marxin (3):
> Encapsulate comp_cost within a class with methods.
> Add profiling support for IVOPTS
> Enhance dumps of IVOPTS
>
> gcc/testsuite/g++.dg/tree-ssa/ivopts-3.C | 2 +-
> gcc/tree-ssa-loop-ivopts.c | 690 ++++++++++++++++++++++---------
> 2 files changed, 491 insertions(+), 201 deletions(-)
>
> --
> 2.8.1
>
prev parent reply other threads:[~2016-05-03 9:28 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-29 11:58 marxin
2016-04-29 11:58 ` [PATCH 3/3] Enhance dumps of IVOPTS marxin
2016-05-06 9:19 ` Martin Liška
2016-05-09 9:47 ` Richard Biener
2016-05-10 13:16 ` Bin.Cheng
2016-05-11 14:18 ` Martin Liška
2016-05-12 12:14 ` Martin Liška
2016-05-12 13:51 ` Bin.Cheng
2016-05-12 16:42 ` Martin Liška
2016-05-13 9:43 ` Bin.Cheng
2016-05-13 10:44 ` Martin Liška
2016-05-13 12:12 ` H.J. Lu
2016-05-13 12:39 ` Martin Liška
2016-05-13 12:44 ` Kyrill Tkachov
2016-05-13 12:47 ` Richard Biener
2016-05-13 12:51 ` Martin Liška
2016-05-13 14:17 ` H.J. Lu
2016-05-13 14:46 ` H.J. Lu
2016-04-29 11:58 ` [PATCH 1/3] Encapsulate comp_cost within a class with methods marxin
2016-05-16 10:14 ` Bin.Cheng
2016-05-16 13:55 ` Martin Liška
2016-05-19 10:23 ` Martin Liška
2016-05-19 11:24 ` Bin.Cheng
2016-05-26 21:02 ` Martin Liška
2016-04-29 11:58 ` [PATCH 2/3] Add profiling support for IVOPTS marxin
2016-05-16 13:56 ` Martin Liška
2016-05-16 22:27 ` Bin.Cheng
2016-05-19 10:28 ` Martin Liška
2016-05-20 10:04 ` Bin.Cheng
2016-05-24 10:19 ` Bin.Cheng
2016-05-24 10:33 ` Bin.Cheng
2016-05-24 11:01 ` Bin.Cheng
2016-05-30 19:51 ` Martin Liška
2016-05-03 9:28 ` Bin.Cheng [this message]
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=CAHFci2_YrsL8k1sTR__Awa6SfV1-vC1fznc7rz_nUFcf7mDfWw@mail.gmail.com \
--to=amker.cheng@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mliska@suse.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).