Ahh, I simplified the test too much, my mistake.
I modified the example <https://go.dev/play/p/_VFUj5y2_xT> and verified
that the profile does capture the inline function:
3.95s 79.16% 79.16% 3.95s 79.16% main.modify (inline)
1.04s 20.84% 100% 4.99s 100% main.main
Thank you
On Saturday 17 February 2024 at 09:27:03 UTC-8 Keith Randall wrote:
> This is a problem with your test. pprof is correct here. Since you never
> use n, when double is inlined its body is compiled completely away.
>
> On Thursday, February 15, 2024 at 10:18:07 PM UTC-8 Prashant V wrote:
>
>> Is it expected that CPU profiles taken with pprof don't include inlined
>> frames?
>>
>> With a simple repro <https://go.dev/play/p/6-JjlhAT14z>, when the
>> `double` function has `go:noinline`, then the pprof shows the double
>> function as expected,
>>
>> 3.34s 67.07% 67.07% 4.98s 100% main.main
>> 1.64s 32.93% 100% 1.64s 32.93% main.double
>>
>> However, when the noinline directive is removed, the double function
>> isn't shown, only the main function is:
>>
>> 4.99s 100% 100% 4.99s 100% main.main
>>
>> Is this an expected limitation of pprof profiles, or this a bug that I
>> should report?
>>
>> Thanks
>>
>
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/golang-nuts/055b81a1-9890-40af-b359-c440769f2d89n%40googlegroups.com.
