Propagate receiver from initial call site to code generator.

src/compiler.h

Index: src/compiler.h
diff --git a/src/compiler.h b/src/compiler.h
index 546e446b98a22e854f75bf94ac56cab89d3e7c7d..74c7ffb1719dfa202c7478593749521d1b006f19 100644
--- a/src/compiler.h
+++ b/src/compiler.h
@@ -70,7 +70,9 @@ class Compiler : public AllStatic {
   // Compile from function info (used for lazy compilation). Returns
   // true on success and false if the compilation resulted in a stack
   // overflow.
-  static bool CompileLazy(Handle<SharedFunctionInfo> shared, int loop_nesting);
+  static bool CompileLazy(Handle<SharedFunctionInfo> shared,
+                          Handle<Object> receiver,

[Kasper Lund, 2010/01/28 16:28:51]

I think you would do yourself a favor by wrapping the receiver in some
stack-allocated structure  that's easier to extend going forward and passing a
pointer to that in instead of the "naked" receiver. Could even contain the
loop_nesting too.

+                          int loop_nesting);
 
   // Compile a function boilerplate object (the function is possibly
   // lazily compiled). Called recursively from a backend code