mirror of
https://github.com/RPCS3/llvm-mirror.git
synced 2025-01-31 20:51:52 +01:00
4aa599e067
In one case, we were handling out of bounds, but not undef indices. In the other, we were handling undef (with the comment making the analogy to out of bounds), but not out of bounds. Be consistent and treat both undef and constant out of bounds indices as producing undefined results. As a side effect, this also protects instcombine from having to handle large constant indices as we always simplify first. llvm-svn: 321575
48 lines
1.1 KiB
LLVM
48 lines
1.1 KiB
LLVM
; NOTE: Assertions have been autogenerated by utils/update_test_checks.py
|
|
; RUN: opt < %s -instsimplify -S | FileCheck %s
|
|
|
|
; Weird Types
|
|
|
|
define i129 @vec_extract_negidx(<3 x i129> %a) {
|
|
; CHECK-LABEL: @vec_extract_negidx(
|
|
; CHECK-NEXT: ret i129 undef
|
|
;
|
|
%E1 = extractelement <3 x i129> %a, i129 -1
|
|
ret i129 %E1
|
|
}
|
|
|
|
define i129 @vec_extract_out_of_bounds(<3 x i129> %a) {
|
|
; CHECK-LABEL: @vec_extract_out_of_bounds(
|
|
; CHECK-NEXT: ret i129 undef
|
|
;
|
|
%E1 = extractelement <3 x i129> %a, i129 3
|
|
ret i129 %E1
|
|
}
|
|
|
|
define i129 @vec_extract_out_of_bounds2(<3 x i129> %a) {
|
|
; CHECK-LABEL: @vec_extract_out_of_bounds2(
|
|
; CHECK-NEXT: ret i129 undef
|
|
;
|
|
%E1 = extractelement <3 x i129> %a, i129 999999999999999
|
|
ret i129 %E1
|
|
}
|
|
|
|
|
|
define i129 @vec_extract_undef_index(<3 x i129> %a) {
|
|
; CHECK-LABEL: @vec_extract_undef_index(
|
|
; CHECK-NEXT: ret i129 undef
|
|
;
|
|
%E1 = extractelement <3 x i129> %a, i129 undef
|
|
ret i129 %E1
|
|
}
|
|
|
|
|
|
define i129 @vec_extract_in_bounds(<3 x i129> %a) {
|
|
; CHECK-LABEL: @vec_extract_in_bounds(
|
|
; CHECK-NEXT: %E1 = extractelement <3 x i129> %a, i129 2
|
|
; CHECK-NEXT: ret i129 %E1
|
|
;
|
|
%E1 = extractelement <3 x i129> %a, i129 2
|
|
ret i129 %E1
|
|
}
|