[stubs] Simplify the non-function case of CallConstructStub.

[stubs] Simplify the non-function case of CallConstructStub.

Currently we do this dance between the CallConstructStub, the
CALL_* builtins and the %GetConstructorDelegate, %GetProxyTrap,
and %Apply runtime functions for every [[Construct]] operation on
non-function callables. This is complexity is unnecessary, and can
be simplified to work without any JS builtin. This will also make it
a lot easier to implement ES6 compliant [[Construct]] for proxies.

Also sanitize the invariant for CallConstructStub, which up until now
always restored the context itself, but that force us to always create
another copy of all arguments in case of proxies and other callables,
so we can relax that constraint by making the caller restore the context
(this only affects fullcodegen, since the optimizing compilers already
properly restore the context anyway).

R=mstarzinger@chromium.org

Committed: https://crrev.com/622fa0ea21b3517b1feaed447c87e580bafac865
Cr-Commit-Position: refs/heads/master@{#30691}

[Benedikt Meurer, 2015-09-11 07:59:36]

Patchset #1 (id:1) has been deleted

[Benedikt Meurer, 2015-09-11 08:00:12]

bmeurer@chromium.org changed reviewers:
+ mstarzinger@chromium.org

[Benedikt Meurer, 2015-09-11 08:00:12]

Hey Michi,

This is the cleanup I mentioned for CALL* builtin removal (getting closer to
zero builtins).
Please take a look.

Thanks,
Benedikt

[Benedikt Meurer, 2015-09-11 08:00:22]

The CQ bit was checked by bmeurer@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2015-09-11 08:00:28]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1335723002/20001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1335723002/20001

[commit-bot: I haz the power, 2015-09-11 08:15:12]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-09-11 08:15:13]

Dry run: Try jobs failed on following builders:
  v8_win_rel on tryserver.v8 (JOB_FAILED,
http://build.chromium.org/p/tryserver.v8/builders/v8_win_rel/builds/9616)

[Benedikt Meurer, 2015-09-11 08:58:24]

Patchset #2 (id:40001) has been deleted

[Michael Starzinger, 2015-09-11 09:17:37]

https://codereview.chromium.org/1335723002/diff/60001/src/arm/code-stubs-arm.cc
File src/arm/code-stubs-arm.cc (right):

https://codereview.chromium.org/1335723002/diff/60001/src/arm/code-stubs-arm....
src/arm/code-stubs-arm.cc:2536: __ str(r1, MemOperand(sp, r0, LSL,
kPointerSizeLog2));
This is confusing. Why do we suddenly need to patch the receiver to point to the
target function? If this is really needed, can we clarify the comment so that
people understand why this patching happens?

[Benedikt Meurer, 2015-09-11 09:20:28]

Fixed.

https://codereview.chromium.org/1335723002/diff/60001/src/arm/code-stubs-arm.cc
File src/arm/code-stubs-arm.cc (right):

https://codereview.chromium.org/1335723002/diff/60001/src/arm/code-stubs-arm....
src/arm/code-stubs-arm.cc:2536: __ str(r1, MemOperand(sp, r0, LSL,
kPointerSizeLog2));
You're right, receiver stays the same.

[Michael Starzinger, 2015-09-11 09:24:25]

LGTM.

[Benedikt Meurer, 2015-09-11 09:24:33]

The CQ bit was checked by bmeurer@chromium.org

[commit-bot: I haz the power, 2015-09-11 09:24:46]

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

[commit-bot: I haz the power, 2015-09-11 09:45:12]

Committed patchset #3 (id:80001)

[commit-bot: I haz the power, 2015-09-11 09:45:35]

Patchset 3 (id:??) landed as
https://crrev.com/622fa0ea21b3517b1feaed447c87e580bafac865
Cr-Commit-Position: refs/heads/master@{#30691}