search for: stepbackward

...> careful about which registers stackmap clients are expected to preserve "no > matter what", and the rest of the LLVM reserved regs (e.g. base pointer) > should just be unconditionally added to the live set. We can continue that > discussion in the PR. > > LivePhysRegs.stepBackward should be completely valid at any point, so if > there are bugs they need to be fixed. LivePhysRegs.stepForward is > conservative and relies on KILL flags so should only be used very early in > the MI pipeline for convenience as an optimization. > StackMapLivenessAnalysis uses stepBack...

Hi all, I've run into a couple bugs recently that affected stackmap liveness analysis in various ways: http://llvm.org/bugs/show_bug.cgi?id=19224 - function arguments stay live unnecessarily http://llvm.org/bugs/show_bug.cgi?id=21265 - eflags can end up as a live out http://llvm.org/bugs/show_bug.cgi?id=21266 - %rip can end up as a live out The first two have nothing to do with stackmaps