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.
24 lines
1.0 KiB
LLVM
24 lines
1.0 KiB
LLVM
; RUN: opt -passes=debugify -S < %s | FileCheck --check-prefixes=ALL,VALUE %s
|
|
; RUN: opt -passes=debugify -debugify-level=locations -S < %s | FileCheck --check-prefixes=ALL --implicit-check-not=dbg.value %s
|
|
|
|
; RUN: opt -passes=debugify -S < %s --try-experimental-debuginfo-iterators | FileCheck --check-prefixes=ALL,VALUE %s
|
|
|
|
; ALL-LABEL: @test
|
|
define void @test() {
|
|
%add = add i32 1, 2
|
|
; ALL-NEXT: %add = add i32 1, 2, !dbg [[L1:![0-9]+]]
|
|
; VALUE-NEXT: call void @llvm.dbg.value(metadata i32 %add, metadata [[add:![0-9]+]], metadata !DIExpression()), !dbg [[L1]]
|
|
%sub = sub i32 %add, 1
|
|
; ALL-NEXT: %sub = sub i32 %add, 1, !dbg [[L2:![0-9]+]]
|
|
; VALUE-NEXT: call void @llvm.dbg.value(metadata i32 %sub, metadata [[sub:![0-9]+]], metadata !DIExpression()), !dbg [[L2]]
|
|
; ALL-NEXT: ret void, !dbg [[L3:![0-9]+]]
|
|
ret void
|
|
}
|
|
|
|
; VALUE: [[add]] = !DILocalVariable
|
|
; VALUE: [[sub]] = !DILocalVariable
|
|
|
|
; ALL: [[L1]] = !DILocation(line: 1, column: 1, scope:
|
|
; ALL: [[L2]] = !DILocation(line: 2, column: 1, scope:
|
|
; ALL: [[L3]] = !DILocation(line: 3, column: 1, scope:
|