Get rid of all non-IC uses of LookupOwnRealNamedProperty

test/cctest/test-api.cc

Index: test/cctest/test-api.cc
diff --git a/test/cctest/test-api.cc b/test/cctest/test-api.cc
index 50ce753db869947089012d42c9710ace2ac70818..73d39cea8dc03c7f7b0359e492eb1e59d7d5c721 100644
--- a/test/cctest/test-api.cc
+++ b/test/cctest/test-api.cc
@@ -21724,7 +21724,6 @@ TEST(AccessCheckThrows) {
 
   // Create a context and set an x property on it's global object.
   LocalContext context0(NULL, global_template);
-  context0->Global()->Set(v8_str("x"), v8_num(42));

[Yang, 2014/08/21 06:08:20]

Is this intentional? Why?

[Toon Verwaest, 2014/08/21 07:02:55]

Because below it's calling into %AddNamedProperty, which due to my changes in
the LookupIterator to look behind the JSGlobalProxy into the JSGlobalObject, now
fails with a runtime assert that the property shouldn't exist yet. Plus given
that all should result in AccessCheck failure, it doesn't really make a
difference whether or not the property is there.

[Yang, 2014/08/21 07:37:26]

Acknowledged.

   v8::Handle<v8::Object> global0 = context0->Global();
 
   // Create a context with a different security token so that the