[llvm] [RFC] Emit dwarf data for signature-changed or new functions (PR #157349)

[Orlando Cazalet-Hyams via llvm-commits]

OCHyams wrote:

Hi, I've read over this thread but haven't managed to build a full picture of what's being introduced here. I see "RFC" in the PR title - has this change been discussed on discourse? It might be worth doing that if you haven't, to raise awareness, if this is going to affect many debug info consumers.

As far as I understand it from the thread, this change intends to add an additional DWARF inline scope to functions with changed signatures, where the inline scope has the original signature. Is that right? If so, isn't that going to cause debuggers to spuriously show an extra "inline" frame in the call stack?

* Do you intend to have this feature (pass?) enabled by default?
* What assumptions in DWARF consumers is this likely to break?




https://github.com/llvm/llvm-project/pull/157349