[llvm] [DwarfDebug] Associate subprogram DIEs with their Functions (PR #162852)

[David Blaikie via llvm-commits]

dwblaikie wrote:

So... I /think/ the original conversations were maybe of the form "we picked the function from one LTO input, but the class from another - and now they don't match" - are there actually cases where we pick /both/ functions (two functions survive LTO that both refer to conceptually the same DISubprogram?)? It sounds like that's what you're proposing supporting - and I'm not sure if that was discussed (if you've got pointers to prior discussions on this, please link it so I can catch back up -sorry for rehashing all this - the timelines are very long & it's hard to keep track of it all :/ ) - it'd be nice if we could avoid the complexity of that if possible.

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