[Interpreter] Bytecode graph builder

src/compiler/linkage.h

Index: src/compiler/linkage.h
diff --git a/src/compiler/linkage.h b/src/compiler/linkage.h
index 57203627887647cbaa1736d45292054d121adbbe..065382471fa82a15716a50c79dc4a682c30e19b4 100644
--- a/src/compiler/linkage.h
+++ b/src/compiler/linkage.h
@@ -330,6 +330,7 @@ class Linkage : public ZoneObject {
 
   // Special parameter indices used to pass fixed register data through
   // interpreter dispatches.
+  static const int kInterpreterReceiverParameter = -1;

[rmcilroy, 2015/09/04 11:35:37]

No, please don't make this an Interpreter parameter - these are only the
parameters which are passed via the Dispatch TailCalls in the bytecode handler.
It should probably be just below kJSFunctionCallClosureParamIndex and be called
something like kJSFunctionRecieverParamIndex (since this is not specific to the
interpreter).

Actually, I'm wondering why this isn't 
Linkage::kJSFunctionCallClosureParamIndex - this seems to be what
ASTGraphBuilder is using for the same thing. Michi, why didn't you want this to
be Linkage::kJSFunctionCallClosureParamIndex?

[oth, 2015/09/04 16:15:46]

Removed. Won't commit until this is resolved. Comment added to
BytecodeGraphBuilder next to -1.

[Michael Starzinger, 2015/09/04 16:35:50]

Receiver and closure are to different things. One refers to whatever "this"
points to. The other refers to the JSFunction that the activation representing.

And I agree this is not a "Parameter" to the handler stub this is a "ParamIndex"
for the function activation, that's again something different.

   static const int kInterpreterAccumulatorParameter = 0;
   static const int kInterpreterRegisterFileParameter = 1;
   static const int kInterpreterBytecodeOffsetParameter = 2;