search for: 119a6bf6

The debug information does try to track what happens to parameters and local variables. In the IR this is done with llvm.dbg.value intrinsic functions, and in Machine IR this is done with DBG_VALUE instructions. These have operands that point to the metadata describing the variable, and the location or value of the variable. Ideally each optimization would preserve this information, unless the

Hi all, I am interested in tracking precisely locations of local variables / function parameters in the binary (whether the variable is on the stack, in a register, or maybe both). I know that this is part of the debug information, which can be potentially dropped by optimization passes. Is there any way to verify after each pass the location of the variable? I mean, right before any