From: Chris Lattner <sabre@nondot.org>
Date: Fri, 24 Mar 2006 18:24:43 +0000 (+0000)
Subject: Fix a bad JIT encoding of VPERM.  Why is VPERM D,A,B,C but vfmadd is D,A,C,B ??
X-Git-Url: http://demsky.eecs.uci.edu/git/?a=commitdiff_plain;h=8edd11f33d1cadfddcd97a74ebdc8c7603266593;p=oota-llvm.git

Fix a bad JIT encoding of VPERM.  Why is VPERM D,A,B,C but vfmadd is D,A,C,B ??


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@27069 91177308-0d34-0410-b5e6-96231b3b80d8
---

diff --git a/lib/Target/PowerPC/PPCInstrInfo.td b/lib/Target/PowerPC/PPCInstrInfo.td
index ff2dc315ac1..5078d392505 100644
--- a/lib/Target/PowerPC/PPCInstrInfo.td
+++ b/lib/Target/PowerPC/PPCInstrInfo.td
@@ -985,9 +985,9 @@ def VNMSUBFP: VAForm_1<47, (ops VRRC:$vD, VRRC:$vA, VRRC:$vC, VRRC:$vB),
                        Requires<[FPContractions]>;
 
 def VPERM   : VAForm_1<43, (ops VRRC:$vD, VRRC:$vA, VRRC:$vC, VRRC:$vB),
-                       "vperm $vD, $vA, $vC, $vB", VecPerm,
+                       "vperm $vD, $vA, $vB, $vC", VecPerm,
                        [(set VRRC:$vD,
-                             (PPCvperm (v4f32 VRRC:$vA), VRRC:$vC, VRRC:$vB))]>;
+                             (PPCvperm (v4f32 VRRC:$vA), VRRC:$vB, VRRC:$vC))]>;
 
 
 // VX-Form instructions.  AltiVec arithmetic ops.