search for: stackmaplivenessanalysi

...R. > > 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 stepBackward so should not depend on KILL > flags at all. LivePhysRegs should not modify any MI operands, so KILL flags > shouldn’t be getting “removed” by anything related to stackmaps or liveness. > > Note that we would like to move to a world where KILL flags are completely &gt...

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

...pare.cpp for Release+Asserts build llvm[2]: Compiling SlotIndexes.cpp for Release+Asserts build llvm[2]: Compiling SpillPlacement.cpp for Release+Asserts build llvm[2]: Compiling SplitKit.cpp for Release+Asserts build llvm[2]: Compiling StackColoring.cpp for Release+Asserts build llvm[2]: Compiling StackMapLivenessAnalysis.cpp for Release+Asserts build llvm[2]: Compiling StackMaps.cpp for Release+Asserts build llvm[2]: Compiling StackProtector.cpp for Release+Asserts build llvm[2]: Compiling StackSlotColoring.cpp for Release+Asserts build llvm[2]: Compiling StatepointExampleGC.cpp for Release+Asserts build llvm[2]:...