[runtime] Initial step towards switching Execution::Call to callable.

[runtime] Initial step towards switching Execution::Call to callable.

Currently Execution::Call (and friends) still duplicate a lot of the
Call sequence logic that should be encapsulated in the Call and
CallFunction builtins. So the plan now is to switch Execution::Call
to accept any Callable and just pass that through to the Call builtin.

CQ_INCLUDE_TRYBOTS=tryserver.v8:v8_linux_nosnap_dbg
R=jarin@chromium.org
BUG=v8:4413
LOG=n

Committed: https://crrev.com/359645f48156e15f235e9a9ede7910e0bcd9ae45
Cr-Commit-Position: refs/heads/master@{#30791}

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

[Benedikt Meurer, 2015-09-17 06:59:02]

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

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

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

[Benedikt Meurer, 2015-09-17 06:59:41]

Hey Jaro,

Next tiny step towards a single bottleneck for the Call sequence; removing magic
on the C++ side of things.
Please take a look.

Thanks,
Benedikt

[Jarin, 2015-09-17 07:23:25]

lgtm

[Benedikt Meurer, 2015-09-17 07:24:17]

The CQ bit was unchecked by bmeurer@chromium.org

[Benedikt Meurer, 2015-09-17 07:24:23]

The CQ bit was checked by bmeurer@chromium.org

[commit-bot: I haz the power, 2015-09-17 07:24:27]

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

[commit-bot: I haz the power, 2015-09-17 09:02:35]

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

[commit-bot: I haz the power, 2015-09-17 09:02:36]

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

[Benedikt Meurer, 2015-09-17 09:03:47]

The CQ bit was checked by bmeurer@chromium.org

[commit-bot: I haz the power, 2015-09-17 09:03:52]

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

[commit-bot: I haz the power, 2015-09-17 09:05:33]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-09-17 09:05:57]

Patchset 1 (id:??) landed as
https://crrev.com/359645f48156e15f235e9a9ede7910e0bcd9ae45
Cr-Commit-Position: refs/heads/master@{#30791}

[Michael Achenbach, 2015-09-17 10:06:44]

Why land with obvious layout test failures? The policy is to fix those
beforehand (if possible) to avoid having those bots red for too long.

[Michael Achenbach, 2015-09-17 10:07:50]

OK - the second test run doesn't show useful results - I admit that. But the
first does:
http://build.chromium.org/p/tryserver.v8/builders/v8_linux_layout_dbg/builds/...

[Michael Achenbach, 2015-09-17 10:11:21]

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

The reason for reverting is: [Sheriff] Causes a dcheck failure in layout tests
(and some test changes in release):
https://storage.googleapis.com/chromium-layout-test-archives/V8-Blink_Linux_6...
from
http://build.chromium.org/p/client.v8.fyi/builders/V8-Blink%20Linux%2064%20%2....

[Benedikt Meurer, 2015-09-17 11:57:59]

The CQ bit was checked by bmeurer@chromium.org

[Benedikt Meurer, 2015-09-17 11:57:59]

The patchset sent to the CQ was uploaded after l-g-t-m from jarin@chromium.org
Link to the patchset: https://codereview.chromium.org/1353723002/#ps20001
(title: "Handle sloppy mode api functions correctly.")

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

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

[commit-bot: I haz the power, 2015-09-17 12:48:48]

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

[commit-bot: I haz the power, 2015-09-17 12:48:48]

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

[Benedikt Meurer, 2015-09-17 17:06:25]

The CQ bit was checked by bmeurer@chromium.org

[commit-bot: I haz the power, 2015-09-17 17:06:39]

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

[Benedikt Meurer, 2015-09-17 17:09:00]

On 2015/09/17 10:07:50, Michael Achenbach wrote:
> OK - the second test run doesn't show useful results - I admit that. But the
> first does:
>
http://build.chromium.org/p/tryserver.v8/builders/v8_linux_layout_dbg/builds/...

Well the webkit test failure appeared (and still appears) on various different
pending CLs, so I was pretty confident that it was unrelated to my CL and
removed the layout bot from the include list (because it was just blocking for a
reason not related to my CL). And the useful results from the second run were
not taken into account by the CQ anymore (the results arrived after the CL was
already in).

[Benedikt Meurer, 2015-09-17 17:09:25]

The CQ bit was unchecked by bmeurer@chromium.org

[Benedikt Meurer, 2015-09-17 17:09:39]

The CQ bit was checked by bmeurer@chromium.org

[commit-bot: I haz the power, 2015-09-17 17:09:58]

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

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

Committed patchset #2 (id:20001)

[Benedikt Meurer, 2015-09-17 17:11:51]

On 2015/09/17 17:09:00, Benedikt Meurer wrote:
> On 2015/09/17 10:07:50, Michael Achenbach wrote:
> > OK - the second test run doesn't show useful results - I admit that. But the
> > first does:
> >
>
http://build.chromium.org/p/tryserver.v8/builders/v8_linux_layout_dbg/builds/...
> 
> Well the webkit test failure appeared (and still appears) on various different
> pending CLs, so I was pretty confident that it was unrelated to my CL and
> removed the layout bot from the include list (because it was just blocking for
a
> reason not related to my CL). And the useful results from the second run were
> not taken into account by the CQ anymore (the results arrived after the CL was
> already in).

Argh sorry I confused myself. It was the second run actually, the one you meant.
I somehow didn't see the first run (the interface only shows the last failing
run by default).

[commit-bot: I haz the power, 2015-09-17 17:12:05]

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