v8: backport 9fb02b526f1cd3b859a530a01adb08bc0d089f4f

[devsnek]

Refs: v8/v8@9fb02b5

Original commit message:

Allow function callbacks to have Proxy as receiver.
R=verwaest@chromium.org
Bug: v8:5773
Change-Id: Ifd29a1116ee8c86b8d8d24485bbfd19e260ab66b
Reviewed-on: chromium-review.googlesource.com/1046088
Commit-Queue: Yang Guo <yangguo@chromium.org>
Reviewed-by: Camillo Bruni <cbruni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#53015}

Checklist

• make -j4 test (UNIX), or vcbuild test (Windows) passes
• commit message follows commit guidelines

[devsnek]

CI: https://ci.nodejs.org/job/node-test-pull-request/14702/
V8 CI: https://ci.nodejs.org/job/node-test-commit-v8-linux/

[devsnek]

landed in 5db018d

[TimothyGu]

For future commits to V8, it would be great if we could cut down the commit hash in the commit message a bit. Also the subsystem is in fact deps.

[targos]

The git node v8 command can help with that. In this case, it would have generated:

 deps: cherry-pick 9fb02b5 from upstream V8
Original commit message:
Allow function callbacks to have Proxy as receiver.
R=verwaest@chromium.org
Bug: v8:5773
Change-Id: Ifd29a1116ee8c86b8d8d24485bbfd19e260ab66b
Reviewed-on: https://chromium-review.googlesource.com/1046088
Commit-Queue: Yang Guo <yangguo@chromium.org>
Reviewed-by: Camillo Bruni <cbruni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#53015}
Refs: https://github.com/v8/v8/commit/9fb02b526f1cd3b859a530a01adb08bc0d089f4f

By the way, we usually say cherry-pick when the change applies cleanly and backport when conflicts have to be resolved manually.