From: Jan Hubicka <hubicka@ucw.cz>
To: "Cui,Lili" <lili.cui@intel.com>
Cc: gcc-patches@gcc.gnu.org, hongtao.liu@intel.com, hongjiu.lu@intel.com
Subject: Re: [PATCH] Add attribute hot judgement for INLINE_HINT_known_hot hint.
Date: Tue, 20 Sep 2022 18:17:01 +0200 [thread overview]
Message-ID: <YynnfftUnaB011D5@kam.mff.cuni.cz> (raw)
In-Reply-To: <20220920084810.25157-1-lili.cui@intel.com>
> Hi Honza,
>
> This patch is to add attribute hot judgement for INLINE_HINT_known_hot hint.
>
> We set up INLINE_HINT_known_hot hint only when we have profile feedback,
> now add function attribute judgement for it, when both caller and callee
> have __attribute__((hot)), we will also set up INLINE_HINT_known_hot hint
> for it.
>
> With this patch applied
> Ratio Codesize
> ADL Multi-copy: 538.imagic_r 16.7% 1.6%
> SPR Multi-copy: 538.imagic_r 15% 1.7%
> ICX Multi-copy: 538.imagic_r 15.2% 1.7%
> CLX Multi-copy: 538.imagic_r 12.7% 1.7%
> Znver3 Multi-copy: 538.imagic_r 10.6% 1.5%
>
> Bootstrap and regtest pending on x86_64-unknown-linux-gnu.
> OK for trunk?
>
> Thanks,
> Lili.
>
> gcc/ChangeLog
>
> * ipa-inline-analysis.cc (do_estimate_edge_time): Add function attribute
> judgement for INLINE_HINT_known_hot hint.
Thank you. Can you please also add a testcase that tests for this.
So you modify imagemagick marking attribute hot on the specific inline?
I will try to also look again at your earlier patch - I had very busy
summer and unfortunately lost track on this one.
Honza
> ---
> gcc/ipa-inline-analysis.cc | 13 +++++++++----
> 1 file changed, 9 insertions(+), 4 deletions(-)
>
> diff --git a/gcc/ipa-inline-analysis.cc b/gcc/ipa-inline-analysis.cc
> index 1ca685d1b0e..7bd29c36590 100644
> --- a/gcc/ipa-inline-analysis.cc
> +++ b/gcc/ipa-inline-analysis.cc
> @@ -48,6 +48,7 @@ along with GCC; see the file COPYING3. If not see
> #include "ipa-utils.h"
> #include "cfgexpand.h"
> #include "gimplify.h"
> +#include "attribs.h"
>
> /* Cached node/edge growths. */
> fast_call_summary<edge_growth_cache_entry *, va_heap> *edge_growth_cache = NULL;
> @@ -249,15 +250,19 @@ do_estimate_edge_time (struct cgraph_edge *edge, sreal *ret_nonspec_time)
> hints = estimates.hints;
> }
>
> - /* When we have profile feedback, we can quite safely identify hot
> - edges and for those we disable size limits. Don't do that when
> - probability that caller will call the callee is low however, since it
> + /* When we have profile feedback or function attribute, we can quite safely
> + identify hot edges and for those we disable size limits. Don't do that
> + when probability that caller will call the callee is low however, since it
> may hurt optimization of the caller's hot path. */
> - if (edge->count.ipa ().initialized_p () && edge->maybe_hot_p ()
> + if ((edge->count.ipa ().initialized_p () && edge->maybe_hot_p ()
> && (edge->count.ipa () * 2
> > (edge->caller->inlined_to
> ? edge->caller->inlined_to->count.ipa ()
> : edge->caller->count.ipa ())))
> + || (lookup_attribute ("hot", DECL_ATTRIBUTES (edge->caller->decl))
> + != NULL
> + && lookup_attribute ("hot", DECL_ATTRIBUTES (edge->callee->decl))
> + != NULL))
> hints |= INLINE_HINT_known_hot;
>
> gcc_checking_assert (size >= 0);
> --
> 2.17.1
>
next prev parent reply other threads:[~2022-09-20 16:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 8:48 Cui,Lili
2022-09-20 16:17 ` Jan Hubicka [this message]
2022-09-21 9:21 ` Cui, Lili
2022-10-08 0:33 ` Ping^1 " Cui, Lili
2022-10-14 6:28 ` Ping^2 " Cui, Lili
2022-10-21 1:52 ` Ping^3 [PATCH V2] " Cui, Lili
2022-10-29 4:28 ` Jeff Law
2022-10-31 1:44 ` Cui, Lili
2022-10-31 16:35 ` 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=YynnfftUnaB011D5@kam.mff.cuni.cz \
--to=hubicka@ucw.cz \
--cc=gcc-patches@gcc.gnu.org \
--cc=hongjiu.lu@intel.com \
--cc=hongtao.liu@intel.com \
--cc=lili.cui@intel.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).