RPCS3/llvm-mirror
1
0
Fork 0
mirror of https://github.com/RPCS3/llvm-mirror.git synced 2024-10-29 23:12:55 +01:00
Code Issues Projects Releases Wiki Activity
de7985179f
llvm-mirror/test/Verifier/range-1.ll

143 lines
2.9 KiB
LLVM
Raw Normal View History

Convert the uses of '|&' to use '2>&1 |' instead, which works on old versions of Bash. In addition, I can back out the change to the lit built-in shell test runner to support this. This should fix the majority of fallout on Darwin, but I suspect there will be a few straggling issues. llvm-svn: 159544
2012-07-02 20:37:59 +02:00
; RUN: not llvm-as < %s -o /dev/null 2>&1 | FileCheck %s
First part of PR12251. Add documentation and verifier support for the range metadata. llvm-svn: 153359
2012-03-24 01:14:51 +01:00
define void @f1(i8* %x) {
entry:
store i8 0, i8* %x, align 1, !range !0
ret void
}
!0 = metadata !{i8 0, i8 1}
[ValueTracking] Extend range metadata to call/invoke Summary: With this patch, range metadata can be added to call/invoke including IntrinsicInst. Previously, it could only be added to load. Rename computeKnownBitsLoad to computeKnownBitsFromRangeMetadata because range metadata is not only used by load. Update the language reference to reflect this change. Test Plan: Add several tests in range-2.ll to confirm the verifier is happy with having range metadata on call/invoke. Add two tests in AddOverFlow.ll to confirm annotating range metadata to call/invoke can benefit InstCombine. Reviewers: meheff, nlewycky, reames, hfinkel, eliben Reviewed By: eliben Subscribers: llvm-commits Differential Revision: http://reviews.llvm.org/D4187 llvm-svn: 211281
2014-06-19 18:50:16 +02:00
; CHECK: Ranges are only for loads, calls and invokes!
First part of PR12251. Add documentation and verifier support for the range metadata. llvm-svn: 153359
2012-03-24 01:14:51 +01:00
; CHECK-NEXT: store i8 0, i8* %x, align 1, !range !0
define i8 @f2(i8* %x) {
entry:
%y = load i8* %x, align 1, !range !1
ret i8 %y
}
!1 = metadata !{}
; CHECK: It should have at least one range!
; CHECK-NEXT: metadata
define i8 @f3(i8* %x) {
entry:
%y = load i8* %x, align 1, !range !2
ret i8 %y
}
!2 = metadata !{i8 0}
; CHECK: Unfinished range!
define i8 @f4(i8* %x) {
entry:
%y = load i8* %x, align 1, !range !3
ret i8 %y
}
!3 = metadata !{double 0.0, i8 0}
; CHECK: The lower limit must be an integer!
define i8 @f5(i8* %x) {
entry:
%y = load i8* %x, align 1, !range !4
ret i8 %y
}
!4 = metadata !{i8 0, double 0.0}
; CHECK: The upper limit must be an integer!
define i8 @f6(i8* %x) {
entry:
%y = load i8* %x, align 1, !range !5
ret i8 %y
}
!5 = metadata !{i32 0, i8 0}
; CHECK: Range types must match load type!
; CHECK: %y = load
define i8 @f7(i8* %x) {
entry:
%y = load i8* %x, align 1, !range !6
ret i8 %y
}
!6 = metadata !{i8 0, i32 0}
; CHECK: Range types must match load type!
; CHECK: %y = load
define i8 @f8(i8* %x) {
entry:
%y = load i8* %x, align 1, !range !7
ret i8 %y
}
!7 = metadata !{i32 0, i32 0}
; CHECK: Range types must match load type!
; CHECK: %y = load
define i8 @f9(i8* %x) {
entry:
%y = load i8* %x, align 1, !range !8
ret i8 %y
}
!8 = metadata !{i8 0, i8 0}
; CHECK: Range must not be empty!
Require intervals in the range metadata to be in a canonical form: They must be non contiguous, non overlapping and sorted by the lower end. While this is technically a backward incompatibility, every frontent currently produces range metadata with a single interval and we don't have any pass that merges intervals yet, so no existing bitcode files should be rejected by this. llvm-svn: 157741
2012-05-31 15:45:46 +02:00
define i8 @f10(i8* %x) {
entry:
%y = load i8* %x, align 1, !range !9
ret i8 %y
}
!9 = metadata !{i8 0, i8 2, i8 1, i8 3}
Fix typos noticed by Benjamin Kramer. Also make the checks stronger and test that we reject ranges that overlap a previous wrapped range. llvm-svn: 157749
2012-05-31 18:04:26 +02:00
; CHECK: Intervals are overlapping
Require intervals in the range metadata to be in a canonical form: They must be non contiguous, non overlapping and sorted by the lower end. While this is technically a backward incompatibility, every frontent currently produces range metadata with a single interval and we don't have any pass that merges intervals yet, so no existing bitcode files should be rejected by this. llvm-svn: 157741
2012-05-31 15:45:46 +02:00
define i8 @f11(i8* %x) {
entry:
%y = load i8* %x, align 1, !range !10
ret i8 %y
}
!10 = metadata !{i8 0, i8 2, i8 2, i8 3}
Fix typos noticed by Benjamin Kramer. Also make the checks stronger and test that we reject ranges that overlap a previous wrapped range. llvm-svn: 157749
2012-05-31 18:04:26 +02:00
; CHECK: Intervals are contiguous
Require intervals in the range metadata to be in a canonical form: They must be non contiguous, non overlapping and sorted by the lower end. While this is technically a backward incompatibility, every frontent currently produces range metadata with a single interval and we don't have any pass that merges intervals yet, so no existing bitcode files should be rejected by this. llvm-svn: 157741
2012-05-31 15:45:46 +02:00
define i8 @f12(i8* %x) {
entry:
%y = load i8* %x, align 1, !range !11
ret i8 %y
}
!11 = metadata !{i8 1, i8 2, i8 -1, i8 0}
Fix typos noticed by Benjamin Kramer. Also make the checks stronger and test that we reject ranges that overlap a previous wrapped range. llvm-svn: 157749
2012-05-31 18:04:26 +02:00
; CHECK: Intervals are not in order
Require intervals in the range metadata to be in a canonical form: They must be non contiguous, non overlapping and sorted by the lower end. While this is technically a backward incompatibility, every frontent currently produces range metadata with a single interval and we don't have any pass that merges intervals yet, so no existing bitcode files should be rejected by this. llvm-svn: 157741
2012-05-31 15:45:46 +02:00
define i8 @f13(i8* %x) {
entry:
%y = load i8* %x, align 1, !range !12
ret i8 %y
}
!12 = metadata !{i8 1, i8 3, i8 5, i8 1}
Fix typos noticed by Benjamin Kramer. Also make the checks stronger and test that we reject ranges that overlap a previous wrapped range. llvm-svn: 157749
2012-05-31 18:04:26 +02:00
; CHECK: Intervals are contiguous
Require intervals in the range metadata to be in a canonical form: They must be non contiguous, non overlapping and sorted by the lower end. While this is technically a backward incompatibility, every frontent currently produces range metadata with a single interval and we don't have any pass that merges intervals yet, so no existing bitcode files should be rejected by this. llvm-svn: 157741
2012-05-31 15:45:46 +02:00
define i8 @f14(i8* %x) {
entry:
%y = load i8* %x, align 1, !range !13
ret i8 %y
}
!13 = metadata !{i8 1, i8 3, i8 5, i8 2}
Fix typos noticed by Benjamin Kramer. Also make the checks stronger and test that we reject ranges that overlap a previous wrapped range. llvm-svn: 157749
2012-05-31 18:04:26 +02:00
; CHECK: Intervals are overlapping
define i8 @f15(i8* %x) {
entry:
%y = load i8* %x, align 1, !range !14
ret i8 %y
}
!14 = metadata !{i8 10, i8 1, i8 12, i8 13}
; CHECK: Intervals are overlapping
define i8 @f16(i8* %x) {
entry:
%y = load i8* %x, align 1, !range !16
ret i8 %y
}
!16 = metadata !{i8 1, i8 3, i8 4, i8 5, i8 6, i8 2}
; CHECK: Intervals are overlapping
define i8 @f17(i8* %x) {
entry:
%y = load i8* %x, align 1, !range !17
ret i8 %y
}
!17 = metadata !{i8 1, i8 3, i8 4, i8 5, i8 6, i8 1}
; CHECK: Intervals are contiguous
Reference in New Issue Copy Permalink