[strong] Add tests for loading from proxy, super, with access checks

[strong] Add tests for loading from proxy, super, with access checks

Followup for https://codereview.chromium.org/1168093002/

These seem to already function correctly without the need for further runtime
changes.

There will be a final follow-up for interceptors.

BUG=v8:3956
LOG=N

Committed: https://crrev.com/ea4e568363f48955e7de6b538e559132e9899c86
Cr-Commit-Position: refs/heads/master@{#29389}

[conradw, 2015-06-18 13:10:47]

Patchset #2 (id:20001) has been deleted

[conradw, 2015-06-18 13:42:13]

conradw@chromium.org changed reviewers:
+ rossberg@chromium.org

[conradw, 2015-06-18 13:42:14]

PTAL

[conradw, 2015-06-18 13:43:13]

On 2015/06/18 13:42:14, conradw wrote:
> PTAL

Landing this should wait until issues with the original CL are resolved, though
:P

[rossberg, 2015-06-30 12:38:03]

lgtm

https://codereview.chromium.org/1193633003/diff/40001/test/cctest/test-api.cc
File test/cctest/test-api.cc (right):

https://codereview.chromium.org/1193633003/diff/40001/test/cctest/test-api.cc...
test/cctest/test-api.cc:21442: TEST(StrongModeAccessChecks) {
Can we also have a test where the access check forbids the access? Just to make
sure that still raises the right exception.

https://codereview.chromium.org/1193633003/diff/40001/test/mjsunit/strong/loa...
File test/mjsunit/strong/load-proxy.js (right):

https://codereview.chromium.org/1193633003/diff/40001/test/mjsunit/strong/loa...
test/mjsunit/strong/load-proxy.js:62:
assertDoesNotThrow(function(){proxy1.foo});
Maybe add an explanatory TODO here that says that this is merely a sanity test,
and probably not the semantics we ultimately want for proxies.

[conradw, 2015-06-30 15:12:56]

https://codereview.chromium.org/1193633003/diff/40001/test/cctest/test-api.cc
File test/cctest/test-api.cc (right):

https://codereview.chromium.org/1193633003/diff/40001/test/cctest/test-api.cc...
test/cctest/test-api.cc:21442: TEST(StrongModeAccessChecks) {
On 2015/06/30 12:38:03, rossberg wrote:
> Can we also have a test where the access check forbids the access? Just to
make
> sure that still raises the right exception.

Done.

https://codereview.chromium.org/1193633003/diff/40001/test/mjsunit/strong/loa...
File test/mjsunit/strong/load-proxy.js (right):

https://codereview.chromium.org/1193633003/diff/40001/test/mjsunit/strong/loa...
test/mjsunit/strong/load-proxy.js:62:
assertDoesNotThrow(function(){proxy1.foo});
On 2015/06/30 12:38:03, rossberg wrote:
> Maybe add an explanatory TODO here that says that this is merely a sanity
test,
> and probably not the semantics we ultimately want for proxies.

Done.

[conradw, 2015-06-30 17:11:28]

The CQ bit was checked by conradw@chromium.org

[conradw, 2015-06-30 17:11:28]

The patchset sent to the CQ was uploaded after l-g-t-m from
rossberg@chromium.org
Link to the patchset: https://codereview.chromium.org/1193633003/#ps80001
(title: "rebase")

[commit-bot: I haz the power, 2015-06-30 17:11:44]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1193633003/80001

[commit-bot: I haz the power, 2015-06-30 17:13:15]

Committed patchset #4 (id:80001)

[commit-bot: I haz the power, 2015-06-30 17:13:30]

Patchset 4 (id:??) landed as
https://crrev.com/ea4e568363f48955e7de6b538e559132e9899c86
Cr-Commit-Position: refs/heads/master@{#29389}

[Michael Achenbach, 2015-06-30 18:42:01]

A revert of this CL (patchset #4 id:80001) has been created in
https://codereview.chromium.org/1218123003/ by machenbach@chromium.org.

The reason for reverting is: [Sheriff] Breaks gc stress:
http://build.chromium.org/p/client.v8/builders/V8%20GC%20Stress%20-%202/build....