9deee6bffa
D141386 changed the semantics of !range metadata to return poison
on violation. If !range is combined with !noundef, violation is
immediate UB instead, matching the old semantics.
In theory, these IR semantics should also carry over into SDAG.
In practice, DAGCombine has at least one key transform that is
invalid in the presence of poison, namely the conversion of logical
and/or to bitwise and/or (c7b537bf09/llvm/lib/CodeGen/SelectionDAG/DAGCombiner.cpp (L11252)).
Ideally, we would fix this transform, but this will require
substantial work to avoid codegen regressions.
In the meantime, avoid transferring !range metadata without
!noundef, effectively restoring the old !range metadata semantics
on the SDAG layer.
Fixes https://github.com/llvm/llvm-project/issues/64589.
Differential Revision: https://reviews.llvm.org/D157685
18 lines
499 B
LLVM
18 lines
499 B
LLVM
; NOTE: Assertions have been autogenerated by utils/update_llc_test_checks.py
|
|
; RUN: llc < %s -mtriple=x86_64-unknown-linux-gnu | FileCheck %s
|
|
|
|
define i1 @foo(ptr %0) {
|
|
; CHECK-LABEL: foo:
|
|
; CHECK: # %bb.0: # %top
|
|
; CHECK-NEXT: movq $-2147483648, %rax # imm = 0x80000000
|
|
; CHECK-NEXT: testq %rax, (%rdi)
|
|
; CHECK-NEXT: sete %al
|
|
; CHECK-NEXT: retq
|
|
top:
|
|
%1 = load i64, ptr %0, !range !0, !noundef !{}
|
|
%2 = icmp ult i64 %1, 2147483648
|
|
ret i1 %2
|
|
}
|
|
|
|
!0 = !{i64 0, i64 10000000000}
|