[PATCH] D23283: Debugging of optimized code: When locals have their address taken as part of a call use their stack slots as location expressions for debug info.

[Adrian Prantl via llvm-commits]

aprantl added a comment.

Everything described by DBG_VALUE instructions is handled by LiveDebugValues etc.
Note, however that llvm::LowerDbgDeclare() currently does not remove all dbg.declare (arrays are skipped, for example).

My concern was that SelectionDAG would enter SDDbgValues describing a FrameIndex into the MMI sidetable, but I just confirmed that this isn't the case. It only calls MMI.setVariableDbgInfo() for dbg.declare instrinsics. So this is fine.


https://reviews.llvm.org/D23283