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

[via llvm-commits]

yonghong-song wrote:

> > is preferred to have a specific pass to
> > add debuginfo and later on dwarf generation can include those
> > new debuginfo
> 
> Could you explain, why a separate module scan in DwarfDebug::endModule() is needed? I thought IR passes execute strictly before AsmPrinter/DWARF emission.

Based on discussion in https://github.com/llvm/llvm-project/pull/127855, the recommendation is not to touch each individual optimization passes to generate new debuginfo, and it is better to have a central place after all major optimization to generate these new debuginfo.


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