Commit 9b4650e9 authored by dcarney@chromium.org's avatar dcarney@chromium.org

remove maynamedaccess checks

R=svenpanne@chromium.org
BUG=

Review URL: https://codereview.chromium.org/12822002

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@13932 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
parent d9ca45b1
......@@ -944,11 +944,7 @@ bool Isolate::MayNamedAccess(JSObject* receiver, Object* key,
if (decision != UNKNOWN) return decision == YES;
// Get named access check callback
// TODO(dcarney): revert
Map* map = receiver->map();
CHECK(map->IsMap());
CHECK(map->constructor()->IsJSFunction());
JSFunction* constructor = JSFunction::cast(map->constructor());
JSFunction* constructor = JSFunction::cast(receiver->map()->constructor());
if (!constructor->shared()->IsApiFunction()) return false;
Object* data_obj =
......
......@@ -768,8 +768,6 @@ MaybeObject* Object::GetProperty(Object* receiver,
// that even though we may not actually end up loading the named
// property from the current object, we still check that we have
// access to it.
// TODO(dcarney): revert.
CHECK(current->IsJSObject());
JSObject* checked = JSObject::cast(current);
if (!heap->isolate()->MayNamedAccess(checked, name, v8::ACCESS_GET)) {
return checked->GetPropertyWithFailedAccessCheck(receiver,
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment