[PassManager] Adjust check lines to account for different printing.

Relax some checks to account for types being printed differently on
different platforms, surfaced by different buildbots.
This commit is contained in:
Florian Hahn
2022-03-09 13:20:15 +00:00
parent 128745cc26
commit 2c7afadb47
2 changed files with 2 additions and 2 deletions

View File

@@ -6,7 +6,7 @@
; CHECK: Stack dump:
; CHECK-NEXT: 0. Program arguments:
; CHECK-NEXT: 1. Running pass 'ModuleToFunctionPassAdaptor' on module
; CHECK-NEXT: 2. Running pass 'PassManager<llvm::Function>' on function '@foo'
; CHECK-NEXT: 2. Running pass 'PassManager<llvm::Function{{.*}}>' on function '@foo'
; CHECK-NEXT: 3. Running pass 'CrashingFunctionPass' on function '@foo'
define void @foo() {

View File

@@ -8,7 +8,7 @@
; CHECK-NEXT: 1. Running pass 'ModuleToFunctionPassAdaptor' on module
; CHECK-NEXT: 2. Running pass 'PassManager<llvm::Function>' on function '@foo'
; CHECK-NEXT: 3. Running pass 'FunctionToLoopPassAdaptor' on function '@foo'
; CHECK-NEXT: 4. Running pass 'PassManager<llvm::Loop, llvm::LoopAnalysisManager, llvm::LoopStandardAnalysisResults &, llvm::LPMUpdater &>' on loop 'loop.header'.
; CHECK-NEXT: 4. Running pass 'PassManager<llvm::Loop,{{.+}}>' on loop 'loop.header'.
; CHECK-NEXT: 5. Running pass 'CrashingLoopPass' on loop 'loop.header'.
define void @foo() {