mirror of
https://github.com/RPCS3/llvm-mirror.git
synced 2024-10-21 03:53:04 +02:00
d783eb73d8
The included test case would return the incorrect results, because the expansion of an shift with a constant shift amount of 0 would generate undefined behavior. This is because ExpandShiftByConstant assumes that all shifts by constants with a value of 0 have already been optimized away. This doesn't happen for opaque constants and usually this isn't a problem, because opaque constants won't take this code path - they are not supposed to. In the case that the opaque constant has to be expanded by the legalizer, the legalizer would drop the opaque flag. In this case we hit the limitations of ExpandShiftByConstant and create incorrect code. This commit fixes the legalizer by not dropping the opaque flag when expanding opaque constants and adding an assertion to ExpandShiftByConstant to catch this not supported case in the future. This fixes <rdar://problem/16718472> llvm-svn: 207304
22 lines
623 B
LLVM
22 lines
623 B
LLVM
; RUN: llc -mcpu=generic -O1 -relocation-model=pic < %s | FileCheck %s
|
|
target datalayout = "e-m:o-p:32:32-f64:32:64-f80:128-n8:16:32-S128"
|
|
target triple = "i686-apple-darwin"
|
|
|
|
define i64 @test_lshr() {
|
|
entry:
|
|
; CHECK-NOT: movl $-1, 16(%esp)
|
|
; CHECK-NOT: movl $-1, %eax
|
|
%retval = alloca i64
|
|
%op1 = alloca i64
|
|
%op2 = alloca i64
|
|
store i64 -6687208052682386272, i64* %op1
|
|
store i64 7106745059734980448, i64* %op2
|
|
%tmp1 = load i64* %op1
|
|
%tmp2 = load i64* %op2
|
|
%tmp = xor i64 %tmp2, 7106745059734980448
|
|
%tmp3 = lshr i64 %tmp1, %tmp
|
|
store i64 %tmp3, i64* %retval
|
|
%tmp4 = load i64* %retval
|
|
ret i64 %tmp4
|
|
}
|