On Mon, Nov 18, 2024 at 10:14 AM Michael Matz <matz@suse.de> wrote:

Hello,

On Mon, 18 Nov 2024, Neal Gompa wrote:

...

It's not just about making accurate profiling easier, it's also about making it cheap. Frame pointers make it so you can sample at any point on a running system.

Just as well as without FP. At least with backtracers that aren't the most lazy imaginable implementation.

...

This is why the Go compiler has had frame pointers on by default for 6 years.

No, it's because the initial developers of the Go ecosystem were too lazy to implement DWARF, or equivalent, unwind info.

I think you should be careful with the word "lazy". You're proscribing a mental context when you know very little of how they worked through their efforts.

...

It's also why other operating systems have frame pointers on for non-x86_32. Linux is the outlier.

Why are you saying this? Windows x64 also doesn't require one.

MSVC does not let you turn off frame pointers on x64. The flag to switch it off does nothing. https://learn.microsoft.com/en-us/cpp/build/reference/oy-frame-pointer-omiss... -- 真実はいつも一つ！/ Always, there's only one truth!