3a39bb96ca
The description of SETCC says /// SetCC operator - This evaluates to a true value iff the condition is /// true. If the result value type is not i1 then the high bits conform /// to getBooleanContents. Without this patch, we sign extended the i1 to the used larger type regardless of getBooleanContents. This resulted in miscompiles, as shown in the attached testcase that ended up returning -1 instead of 1 when using -mattr=+v. Fixes https://github.com/llvm/llvm-project/issues/55168 Reviewed By: craig.topper Differential Revision: https://reviews.llvm.org/D124618
18 lines
739 B
LLVM
18 lines
739 B
LLVM
; NOTE: Assertions have been autogenerated by utils/update_llc_test_checks.py
|
|
; RUN: llc -start-after codegenprepare -mtriple=riscv64 -mattr=-v -o - %s | FileCheck %s
|
|
; RUN: llc -start-after codegenprepare -mtriple=riscv64 -mattr=+v -o - %s | FileCheck %s
|
|
|
|
; Reproducer for https://github.com/llvm/llvm-project/issues/55168.
|
|
; We should always return 1 (and not -1).
|
|
define i32 @test(i32 %call.i) {
|
|
; CHECK-LABEL: test:
|
|
; CHECK: # %bb.0:
|
|
; CHECK-NEXT: li a0, 1
|
|
; CHECK-NEXT: ret
|
|
%t2 = insertelement <2 x i32> <i32 poison, i32 -2147483648>, i32 %call.i, i64 0
|
|
%t3 = icmp slt <2 x i32> %t2, <i32 -2147483646, i32 -2147483646>
|
|
%t4 = zext <2 x i1> %t3 to <2 x i32>
|
|
%t6 = extractelement <2 x i32> %t4, i64 1
|
|
ret i32 %t6
|
|
}
|