mirror of
https://github.com/RPCS3/llvm-mirror.git
synced 2024-11-25 20:23:11 +01:00
7dfabff224
This is the DAG node for SIGN_EXTEND_INREG :
t21: v4i32 = sign_extend_inreg t18, ValueType:ch:v4i16
It has two operands. The first one is the value it want to extend, and the second
one is the type to specify how to extend the value. For this example, it means
that, it is signed extend the t18(v4i32) from v4i16 to v4i32. That is
the semantics of c code:
vector int foo(vector int m) {
return m << 16 >> 16;
}
And it could be any vector type that hardware support the operation, though
the type 'v4i16' is NOT legal for the target. When we are trying to combine
the srl + sra, what we did now is calling the TLI.isOperationLegal(), which
will also check the legality of the type. That doesn't make sense.
Differential Revision: https://reviews.llvm.org/D70230
23 lines
909 B
LLVM
23 lines
909 B
LLVM
; NOTE: Assertions have been autogenerated by utils/update_llc_test_checks.py
|
|
; RUN: llc -verify-machineinstrs -mtriple=powerpc64le-unknown-linux-gnu -mcpu=pwr9 < %s | FileCheck -check-prefix=CHECK-P9 %s
|
|
; RUN: llc -verify-machineinstrs -mtriple=powerpc64le-unknown-linux-gnu -mcpu=pwr8 < %s | FileCheck -check-prefix=CHECK-P8 %s
|
|
define <4 x i32> @test_signext_vector_inreg(<4 x i16> %n) {
|
|
; CHECK-P9-LABEL: test_signext_vector_inreg:
|
|
; CHECK-P9: # %bb.0: # %entry
|
|
; CHECK-P9-NEXT: vmrglh 2, 2, 2
|
|
; CHECK-P9-NEXT: vextsh2w 2, 2
|
|
; CHECK-P9-NEXT: blr
|
|
;
|
|
; CHECK-P8-LABEL: test_signext_vector_inreg:
|
|
; CHECK-P8: # %bb.0: # %entry
|
|
; CHECK-P8-NEXT: vmrglh 2, 2, 2
|
|
; CHECK-P8-NEXT: vspltisw 3, 8
|
|
; CHECK-P8-NEXT: vadduwm 3, 3, 3
|
|
; CHECK-P8-NEXT: vslw 2, 2, 3
|
|
; CHECK-P8-NEXT: vsraw 2, 2, 3
|
|
; CHECK-P8-NEXT: blr
|
|
entry:
|
|
%0 = sext <4 x i16> %n to <4 x i32>
|
|
ret <4 x i32> %0
|
|
}
|