maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/llvm/test/MC/Hexagon/double-vector-producer.s

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

13 lines
296 B
ArmAsm
Raw Normal View History

[Hexagon] New HVX target features. This patch lets the llvm tools handle the new HVX target features that are added by frontend (clang). The target-features are of the form "hvx-length64b" for 64 Byte HVX mode, "hvx-length128b" for 128 Byte mode HVX. "hvx-double" is an alias to "hvx-length128b" and is soon will be deprecated. The hvx version target feature is upgated form "+hvx" to "+hvxv{version_number}. Eg: "+hvxv62" For the correct HVX code generation, the user must use the following target features. For 64B mode: "+hvxv62" "+hvx-length64b" For 128B mode: "+hvxv62" "+hvx-length128b" Clang picks a default length if none is specified. If for some reason, no hvx-length is specified to llvm, the compilation will bail out. There is a corresponding clang patch. Differential Revision: https://reviews.llvm.org/D38851 llvm-svn: 316101
2017-10-19 02:07:07 +08:00
# RUN: llvm-mc -arch=hexagon -mcpu=hexagonv60 -mhvx -filetype=obj %s | llvm-objdump -d - | FileCheck %s
[Hexagon] Handle double-vector registers as new-value producers Patch by Colin LeMahieu. llvm-svn: 267897
2016-04-28 23:54:48 +08:00
{
v1:0 = vshuff(v1,v0,r7)
v2.w = vadd(v13.w,v15.w)
v3.w = vadd(v8.w,v14.w)
vmem(r2+#-2) = v0.new
}
# CHECK: 60 61 07 1b
# CHECK: 02 4d 4f 1c
# CHECK: 03 48 4e 1c
# CHECK: 26 e6 22 28