mirror of
https://github.com/RPCS3/llvm-mirror.git
synced 2024-11-22 10:42:39 +01:00
d577e2748f
Sometimes a transformation can change the name of some IR (e.g. an SCC with functions added/removed). This can be confusing when debug logging doesn't match the post-transformation name. The specific example I came across was that --print-after-all said the inliner was working on an SCC that only contained one function, but calls in multiple functions were getting inlined. After all inlining, the current SCC only contained one function. Piggyback off of the existing logic to handle invalidated IR + --print-module-scope. Simply always store the IR description and use that. Reviewed By: jamieschmeiser Differential Revision: https://reviews.llvm.org/D106290
27 lines
970 B
LLVM
27 lines
970 B
LLVM
; Make sure that Loop which was invalidated by loop-deletion
|
|
; does not lead to problems for -print-after-all and is just skipped.
|
|
;
|
|
; RUN: opt < %s -disable-output \
|
|
; RUN: -passes=loop-instsimplify -print-after-all 2>&1 | FileCheck %s -check-prefix=SIMPLIFY
|
|
; RUN: opt < %s -disable-output \
|
|
; RUN: -passes=loop-deletion,loop-instsimplify -print-after-all 2>&1 | FileCheck %s -check-prefix=DELETED
|
|
; RUN: opt < %s -disable-output \
|
|
; RUN: -passes=loop-deletion,loop-instsimplify -print-after-all -print-module-scope 2>&1 | FileCheck %s -check-prefix=DELETED
|
|
;
|
|
; SIMPLIFY: IR Dump {{.*}} LoopInstSimplifyPass
|
|
; DELETED: IR Dump {{.*}}LoopDeletionPass {{.*}}(invalidated)
|
|
; DELETED-NOT: IR Dump {{.*}}LoopInstSimplifyPass
|
|
|
|
define void @deleteme() {
|
|
entry:
|
|
br label %loop
|
|
loop:
|
|
%iv = phi i32 [ 0, %entry ], [ %iv.next, %loop ]
|
|
%iv.next = add i32 %iv, 1
|
|
%check = icmp ult i32 %iv.next, 3
|
|
br i1 %check, label %loop, label %exit
|
|
exit:
|
|
ret void
|
|
}
|
|
|