
The only interesting test change is in @PR31262, where the following fold is now performed, while it previously was not: https://alive2.llvm.org/ce/z/a5Qmr6 llvm/test/Transforms/InstSimplify/ConstProp/gep.ll has not been updated, because there is a tradeoff between folding and inrange preservation there that we may want to discuss. Updates have been performed using: https://gist.github.com/nikic/98357b71fd67756b0f064c9517b62a34
25 lines
765 B
LLVM
25 lines
765 B
LLVM
; NOTE: Assertions have been autogenerated by utils/update_test_checks.py
|
|
; RUN: opt -S -passes=instsimplify < %s | FileCheck %s
|
|
|
|
target datalayout = "A5"
|
|
|
|
; A 0 valued byval pointer may be valid
|
|
define i1 @byval_may_be_zero(ptr addrspace(5) byval(i32) %ptr) {
|
|
; CHECK-LABEL: @byval_may_be_zero(
|
|
; CHECK-NEXT: [[CMP:%.*]] = icmp eq ptr addrspace(5) [[PTR:%.*]], null
|
|
; CHECK-NEXT: ret i1 [[CMP]]
|
|
;
|
|
%cmp = icmp eq ptr addrspace(5) %ptr, null
|
|
ret i1 %cmp
|
|
}
|
|
|
|
; FIXME: The interpretation of nonnull assumes a 0 pointer value, so
|
|
; this really is an incorrect fold.
|
|
define i1 @nonnull_may_be_zero(ptr addrspace(5) nonnull %ptr) {
|
|
; CHECK-LABEL: @nonnull_may_be_zero(
|
|
; CHECK-NEXT: ret i1 false
|
|
;
|
|
%cmp = icmp eq ptr addrspace(5) %ptr, null
|
|
ret i1 %cmp
|
|
}
|