[llvm-dev] [LLVMdev] Improving the quality of debug locations / DbgValueHistoryCalculator
Adrian Prantl via llvm-dev
llvm-dev at lists.llvm.org
Wed May 11 13:16:20 PDT 2016
> On May 11, 2016, at 1:12 PM, Francois Pichet <pichet2000 at gmail.com> wrote:
> Regarding the problem of debug range for optimized code.
> Currently a DEBUG_VALUE will be inserted after the <def>vregX
> DEBUG_VALUE are only valid until the end of the current MachineBasicBlock. That's the main problem.
> Why not simply iterate over all uses of vregX and insert an DEBUG_VALUE in all the MachineBasicBlocks where vregX is used. (pre regalloc)
> I prototyped a small pass to do that and at first it seems to improve .debug_loc range validity and enhance the debugging experience for optimized code.
This thread is almost a year old now :-)
Have you looked at the LiveDebugValues pass that resulted from this conversation since?
> On Wed, Aug 12, 2015 at 11:11 AM, Vikram TV via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote:
> Hi all,
> An early implementation of extending debug ranges and providing multiple location support is done here: http://reviews.llvm.org/D11933 <http://reviews.llvm.org/D11933>
> Design document: https://docs.google.com/document/d/1noDVWTvTWBdYdweICPBwvwyt8QvX4KHl7j3XKNSg1nE/edit?usp=sharing <https://docs.google.com/document/d/1noDVWTvTWBdYdweICPBwvwyt8QvX4KHl7j3XKNSg1nE/edit?usp=sharing>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the llvm-dev