Refactor calls to CALL_HEAP_FUNCTION.

src/objects.cc

Index: src/objects.cc
diff --git a/src/objects.cc b/src/objects.cc
index 0defde3e074755f213547fce7f41cb27351105b0..b47ae5ca3f56629ed7aa1cd16a6e3f380fb74ee2 100644
--- a/src/objects.cc
+++ b/src/objects.cc
@@ -5987,25 +5987,6 @@ void JSObject::SetObserved(Handle<JSObject> object) {
 }
 
 
-Handle<JSObject> JSObject::Copy(Handle<JSObject> object,
-                                Handle<AllocationSite> site) {
-  Isolate* isolate = object->GetIsolate();
-  CALL_HEAP_FUNCTION(isolate,
-                     isolate->heap()->CopyJSObject(
-                         *object,
-                         site.is_null() ? NULL : *site),
-                     JSObject);
-}
-
-
-Handle<JSObject> JSObject::Copy(Handle<JSObject> object) {
-  Isolate* isolate = object->GetIsolate();
-  CALL_HEAP_FUNCTION(isolate,
-                     isolate->heap()->CopyJSObject(*object, NULL),
-                     JSObject);
-}
-
-
 Handle<Object> JSObject::FastPropertyAt(Handle<JSObject> object,
                                         Representation representation,
                                         int index) {
@@ -6074,7 +6055,7 @@ MaybeHandle<JSObject> JSObjectWalkVisitor<ContextObject>::StructureWalk(
     if (site_context()->ShouldCreateMemento(object)) {
       site_to_pass = site_context()->current();
     }
-    copy = JSObject::Copy(object, site_to_pass);
+    copy = isolate->factory()->CopyJSObjectWithMemento(object, site_to_pass);

[mvstanton, 2014/04/28 15:41:10]

I think this method should be called CopyJSObjectWithAllocationSite(), because
although it's true that mementos (there can be more than one when depth > 1) may
be emitted, the allocation site is really in charge. In fact, mementos could
become a thing of the past, and the tracking mechanism becomes maintained in
some other way.

   } else {
     copy = object;
   }