Emit VMLA for multiply-add on ARM

src/arm/lithium-arm.h

Index: src/arm/lithium-arm.h
diff --git a/src/arm/lithium-arm.h b/src/arm/lithium-arm.h
index 0ba5e45a8fe1c67b99c9e197d89c53a088410fc5..3e4eef3549d731c787cb0796661dae02e86f732e 100644
--- a/src/arm/lithium-arm.h
+++ b/src/arm/lithium-arm.h
@@ -135,6 +135,7 @@ class LCodeGen;
   V(MathMinMax)                                 \
   V(ModI)                                       \
   V(MulI)                                       \
+  V(MultiplyAddD)                               \
   V(NumberTagD)                                 \
   V(NumberTagI)                                 \
   V(NumberTagU)                                 \
@@ -621,6 +622,22 @@ class LMulI: public LTemplateInstruction<1, 2, 1> {
 };
 
 
+class LMultiplyAddD: public LTemplateInstruction<1, 3, 0> {
+ public:
+  LMultiplyAddD(LOperand* c, LOperand *a, LOperand* b) {

[Sven Panne, 2012/11/13 13:03:52]

Can we use something less cryptic for the operands like factor1, factor2 and
summand? Or are a/b/c standard names in some ARM and/or GCC documentation?

[Jakob Kummerow, 2012/11/13 13:05:21]

I'd appreciate a comment here what the three operands are used for ("Computes c
+= a * b" or something like that).

Oh, and a nit: "LOperand* a"

[hans, 2012/11/13 14:59:58]

Done.

[hans, 2012/11/13 14:59:58]

Done.

+    inputs_[0] = c;
+    inputs_[1] = a;
+    inputs_[2] = b;
+  }
+
+  LOperand* c() { return inputs_[0]; }
+  LOperand* a() { return inputs_[1]; }
+  LOperand* b() { return inputs_[2]; }
+
+  DECLARE_CONCRETE_INSTRUCTION(MultiplyAddD, "multiply-add-d")
+};
+
+
 class LCmpIDAndBranch: public LControlInstruction<2, 0> {
  public:
   LCmpIDAndBranch(LOperand* left, LOperand* right) {