Make FastNewFunctionContextStub take slots parameter

src/arm/interface-descriptors-arm.cc

Index: src/arm/interface-descriptors-arm.cc
diff --git a/src/arm/interface-descriptors-arm.cc b/src/arm/interface-descriptors-arm.cc
index da979c45d9d95695cb10a6259a19060d52d606ba..172d0fcb5b7d3bb713bf72f8b423a79a45246c8e 100644
--- a/src/arm/interface-descriptors-arm.cc
+++ b/src/arm/interface-descriptors-arm.cc
@@ -22,6 +22,11 @@ void CallInterfaceDescriptor::DefaultInitializePlatformSpecific(
                                    default_stub_registers);
 }
 
+const Register FastNewFunctionContextDescriptor::FunctionRegister() {
+  return r1;
+}
+const Register FastNewFunctionContextDescriptor::SlotsRegister() { return r0; }

[rmcilroy, 2016/07/27 11:11:38]

I see this is used only for lithium-codegen and full-codegen. I wonder whether
the logic for context creation could be moved to hydrogen for Crankshaft use
GetCallInterfaceDescriptor().GetRegisterParameter(0) in full-codegen (e.g., see
FastNewClosureStub). 

Maybe have a chat with Michi or Benedikt about the best plan here since I don't
know the potential issues with crankshaft at all.

[klaasb, 2016/07/27 17:06:31]

As agreed offline, it doesn't seem worth it and easily doable.

+
 const Register LoadDescriptor::ReceiverRegister() { return r1; }
 const Register LoadDescriptor::NameRegister() { return r2; }
 const Register LoadDescriptor::SlotRegister() { return r0; }
@@ -73,12 +78,6 @@ void FastNewClosureDescriptor::InitializePlatformSpecific(
   data->InitializePlatformSpecific(arraysize(registers), registers);
 }
 
-void FastNewFunctionContextDescriptor::InitializePlatformSpecific(
-    CallInterfaceDescriptorData* data) {
-  Register registers[] = {r1};
-  data->InitializePlatformSpecific(arraysize(registers), registers);
-}
-
 void FastNewObjectDescriptor::InitializePlatformSpecific(
     CallInterfaceDescriptorData* data) {
   Register registers[] = {r1, r3};