[llvm] r175023 - Debug Info: LiveDebugVarible can remove DBG_VALUEs, make sure we emit them back.

[Jakob Stoklund Olesen]

On Feb 12, 2013, at 7:01 PM, Eric Christopher <echristo at gmail.com> wrote:

> My idea is that we could track what location it is separately via abi and encode that and then any changes, but I was mostly thinking of not copying the incoming value into an alloca in the front end and rather having the dbg.value reference the function argument rather than the alloca. I'm not sure what changes we'd need to make in allocation to track this though offhand, my guess is some. The dbg.value on entry should have the function argument via the prologue (or we just add them as part of the prologue) which will have the ABI location and then any changes later would be marked by a dbg.value as well if we spilled or killed the argument value (in the case of unused arguments), but we'd be correct at the end of the prologue.
> 
> Sound plausible?

Are you thinking of -O0 code here? The LDV pass and the coalescer only run when optimizing.

/jakob

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20130212/27d38773/attachment.html>