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 func
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,
On Wed, Jun 23, 2021 at 6:15 AM 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 ;)
Here's another case that coincidentally came up yesterday. How should
these attributes behave in the case of __attribu
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.
>
> Similarly to e.g. sanitizer attributes, we sould prevent inlining when one
> function
> is marked as not instrumented. We should do that with -fprofile-generate only.
>
> Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
>
> Ready to be installed?
> Thanks,
> M
Hello.
Similarly to e.g. sanitizer attributes, we sould prevent inlining when one
function
is marked as not instrumented. We should do that with -fprofile-generate only.
Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
Ready to be installed?
Thanks,
Martin
Adds test-case
