summaryrefslogtreecommitdiffstats
path: root/llvm/test
diff options
context:
space:
mode:
authorBill Schmidt <wschmidt@linux.vnet.ibm.com>2013-03-28 19:27:24 +0000
committerBill Schmidt <wschmidt@linux.vnet.ibm.com>2013-03-28 19:27:24 +0000
commit74b2e72ab3743ff64410d273ef7fdda30e9e85bb (patch)
tree609a94327b7110f2394f162f9d35872de2e5eed0 /llvm/test
parent31d2956510b8484373fe244547b4f811430a28ff (diff)
downloadbcm5719-llvm-74b2e72ab3743ff64410d273ef7fdda30e9e85bb.tar.gz
bcm5719-llvm-74b2e72ab3743ff64410d273ef7fdda30e9e85bb.zip
Use direct types in most PowerPC Altivec instructions and patterns.
This follows up Ulrich Weigand's work in PPCInstrInfo.td and PPCInstr64Bit.td by doing the corresponding work for most of the Altivec patterns. I have not been able to do anything for the following classes of instructions: (1) Vector logicals. These don't have corresponding intrinsics and don't have a single obvious vector type. So far as I can tell I need to leave these as VRRC. Affected instructions are: VAND, VANDC, VNOR, VOR, VXOR, V_SET0. (2) Instructions that make use of vector shuffle. The selection code promotes all shuffles to v16i8, so any pattern that matches on a shuffle is constrained. I haven't found any way to make the patterns match on their natural types, so I plan to leave these as VRRC. Affected instructions are: VMRG*, VSPLTB, VSPLTH, VSPLTW, VPKUHUM, VPKUWUM. No change in behavior is anticipated. llvm-svn: 178277
Diffstat (limited to 'llvm/test')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud