2caaec65c0
Due to an improvement to name preservation, a lot of InstCombine tests now show spurious diffs when regenerated. Rather than regenerating individual files when they get touched, mass-regenerate all UTC-based InstCombine tests. I have then reset a number of files showing suspicious diffs where the UTC output has clearly been manually adjusted. I apologize if I missed anything in the mass of changes.
45 lines
984 B
LLVM
45 lines
984 B
LLVM
; NOTE: Assertions have been autogenerated by utils/update_test_checks.py
|
|
; RUN: opt < %s -passes=instcombine -S | FileCheck %s
|
|
|
|
@g = global i32 0
|
|
|
|
; PR30486
|
|
define i32 @single_case() {
|
|
; CHECK-LABEL: @single_case(
|
|
; CHECK-NEXT: switch i32 ptrtoint (ptr @g to i32), label [[X:%.*]] [
|
|
; CHECK-NEXT: ]
|
|
; CHECK: x:
|
|
; CHECK-NEXT: ret i32 0
|
|
;
|
|
switch i32 add (i32 ptrtoint (ptr @g to i32), i32 -1), label %x []
|
|
x:
|
|
ret i32 0
|
|
}
|
|
|
|
define i32 @multiple_cases() {
|
|
; CHECK-LABEL: @multiple_cases(
|
|
; CHECK-NEXT: switch i32 ptrtoint (ptr @g to i32), label [[X:%.*]] [
|
|
; CHECK-NEXT: i32 2, label [[ONE:%.*]]
|
|
; CHECK-NEXT: i32 3, label [[TWO:%.*]]
|
|
; CHECK-NEXT: ]
|
|
; CHECK: x:
|
|
; CHECK-NEXT: ret i32 0
|
|
; CHECK: one:
|
|
; CHECK-NEXT: ret i32 1
|
|
; CHECK: two:
|
|
; CHECK-NEXT: ret i32 2
|
|
;
|
|
switch i32 add (i32 ptrtoint (ptr @g to i32), i32 -1), label %x [
|
|
i32 1, label %one
|
|
i32 2, label %two
|
|
]
|
|
x:
|
|
ret i32 0
|
|
|
|
one:
|
|
ret i32 1
|
|
|
|
two:
|
|
ret i32 2
|
|
}
|