From: Jeff Law <jeffreyalaw@gmail.com>
To: "Martin Liška" <mliska@suse.cz>, "Jan Hubicka" <hubicka@ucw.cz>
Cc: gcc-patches@gcc.gnu.org, Nick Desaulniers <ndesaulniers@google.com>
Subject: Re: [PATCH] inline: do not inline when no_profile_instrument_function is different
Date: Mon, 6 Sep 2021 11:06:34 -0600 [thread overview]
Message-ID: <e28286e1-27f0-8f88-ffca-9c9f9c897f65@gmail.com> (raw)
In-Reply-To: <eead9e43-623e-9452-f69a-b22e160406ce@suse.cz>
On 8/18/2021 2:38 AM, Martin Liška wrote:
> On 6/23/21 3:15 PM, Martin Liška wrote:
>> On 6/23/21 2:38 PM, Jan Hubicka wrote:
>>> Is there reason to prevent the inlining once instrumentation is done?
>>
>> No ;)
>>
>>> I think you can just block it for early inliner.
>>
>> Sure. Do you have a handy predicate function that tells if einliner
>> is done?
>>
>> Thanks,
>> Martin
>
> Hello.
>
> There's updated version of that patch that blocks inlining only during
> einline IPA pass.
>
> Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
>
> Ready to be installed?
> Thanks,
> Martin
>
> 0001-inline-do-not-einline-when-no_profile_instrument_fun.patch
>
> From e2adaff9ed92bcc380e1368418da5ad2801fef4e Mon Sep 17 00:00:00 2001
> From: Martin Liska <mliska@suse.cz>
> Date: Tue, 22 Jun 2021 10:09:01 +0200
> Subject: [PATCH] inline: do not einline when no_profile_instrument_function is
> different
>
> PR gcov-profile/80223
>
> gcc/ChangeLog:
>
> * ipa-inline.c (can_inline_edge_p): Similarly to sanitizer
> options, do not inline when no_profile_instrument_function
> attributes are different in early inliner. It's fine to inline
> it after PGO instrumentation.
OK
jeff
next prev parent reply other threads:[~2021-09-06 17:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-23 11:53 Martin Liška
2021-06-23 12:38 ` Jan Hubicka
2021-06-23 13:15 ` Martin Liška
2021-06-25 19:00 ` Nick Desaulniers
2021-08-18 8:38 ` Martin Liška
2021-09-06 17:06 ` Jeff Law [this message]
2021-09-07 20:41 ` [Committed] Fix fatal typo in gcc.dg/no_profile_instrument_function-attr-2.c Hans-Peter Nilsson
2021-09-08 7:29 ` Martin Liška
2021-09-08 11:25 ` Hans-Peter Nilsson
2021-09-08 11:31 ` Rainer Orth
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=e28286e1-27f0-8f88-ffca-9c9f9c897f65@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=mliska@suse.cz \
--cc=ndesaulniers@google.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).