mono/linux-packaging-mono
0
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Imported Upstream version 5.18.0.167

Browse Source 
Former-commit-id: 289509151e0fee68a1b591a20c9f109c3c789d3a
This commit is contained in:
Xamarin Public Jenkins (auto-signing)
2018-10-20 08:25:10 +00:00
parent e19d552987
commit b084638f15
28489 changed files with 184 additions and 3866856 deletions
Download Patch File Download Diff File Expand all files Collapse all files

58
external/llvm/test/Transforms/JumpThreading/conservative-lvi.ll vendored
View File

@ -1,58 +0,0 @@
; RUN: opt -jump-threading -S %s | FileCheck %s
; Check that we thread arg2neg -> checkpos -> end.
;
; LazyValueInfo would previously fail to analyze the value of %arg in arg2neg
; because its predecessing blocks (checkneg) hadn't been processed yet (PR21238)
; CHECK-LABEL: @test_jump_threading
; CHECK: arg2neg:
; CHECK-NEXT: br i1 %arg1, label %end, label %checkpos.thread
; CHECK: checkpos.thread:
; CHECK-NEXT: br label %end
define i32 @test_jump_threading(i1 %arg1, i32 %arg2) {
checkneg:
%cmp = icmp slt i32 %arg2, 0
br i1 %cmp, label %arg2neg, label %checkpos
arg2neg:
br i1 %arg1, label %end, label %checkpos
checkpos:
%cmp2 = icmp sgt i32 %arg2, 0
br i1 %cmp2, label %arg2pos, label %end
arg2pos:
br label %end
end:
%0 = phi i32 [ 1, %arg2neg ], [ 2, %checkpos ], [ 3, %arg2pos ]
ret i32 %0
}
; arg2neg has an edge back to itself. If LazyValueInfo is not careful when
; visiting predecessors, it could get into an infinite loop.
; CHECK-LABEL: test_infinite_loop
define i32 @test_infinite_loop(i1 %arg1, i32 %arg2) {
checkneg:
%cmp = icmp slt i32 %arg2, 0
br i1 %cmp, label %arg2neg, label %checkpos
arg2neg:
br i1 %arg1, label %arg2neg, label %checkpos
checkpos:
%cmp2 = icmp sgt i32 %arg2, 0
br i1 %cmp2, label %arg2pos, label %end
arg2pos:
br label %end
end:
%0 = phi i32 [ 2, %checkpos ], [ 3, %arg2pos ]
ret i32 %0
}