d2d9dc8eb4
Debugify is extremely useful as a testing and debugging tool, and a good number of LLVM-IR transform tests use it. We need it to support "new" non-instruction debug-info to get test coverage, but it's not important enough to completely convert right now (and it'd be a large undertaking). Thus: convert to/from dbg.value/DPValue mode on entry and exit of the pass, which gives us the functionality without any further work. The cost is compile-time, but again this is only happening during tests. Tested by: the large set of debugify tests enabled here. Note the InstCombine test (cast-mul-select.ll) that hasn't been fully enabled: this is because there's a debug-info sinking piece of code there that hasn't been instrumented.
28 lines
1.1 KiB
LLVM
28 lines
1.1 KiB
LLVM
; NOTE: Assertions have been autogenerated by utils/update_test_checks.py
|
|
; RUN: opt < %s -passes='debugify,function(loop-mssa(licm))' -S | FileCheck %s
|
|
; RUN: opt < %s -passes='debugify,function(loop-mssa(licm))' -S --try-experimental-debuginfo-iterators | FileCheck %s
|
|
|
|
%Ty = type { i32, i32 }
|
|
@X2 = external global %Ty
|
|
|
|
; The GEP in dead1 is adding a zero offset, so the DIExpression can be kept as
|
|
; a "register location".
|
|
; The GEP in dead2 is adding a 4 bytes to the pointer, so the DIExpression is
|
|
; turned into an "implicit location" using DW_OP_stack_value.
|
|
define void @test11() {
|
|
; CHECK-LABEL: @test11(
|
|
; CHECK-NEXT: br label [[LOOP:%.*]], !dbg [[DBG11:![0-9]+]]
|
|
; CHECK: Loop:
|
|
; CHECK-NEXT: call void @llvm.dbg.value(metadata ptr @X2, metadata [[META9:![0-9]+]], metadata !DIExpression(DW_OP_plus_uconst, 4, DW_OP_stack_value)), !dbg [[DBG12:![0-9]+]]
|
|
; CHECK-NEXT: br i1 false, label [[LOOP]], label [[OUT:%.*]], !dbg [[DBG13:![0-9]+]]
|
|
; CHECK: Out:
|
|
; CHECK-NEXT: ret void, !dbg [[DBG14:![0-9]+]]
|
|
;
|
|
br label %Loop
|
|
Loop:
|
|
%dead2 = getelementptr %Ty, ptr @X2, i64 0, i32 1
|
|
br i1 false, label %Loop, label %Out
|
|
Out:
|
|
ret void
|
|
}
|