[turbofan] Materialize JSFunction from frame if possible.

[turbofan] Materialize JSFunction from frame if possible.

This reduces the overhead of recursive calls when context specialization
is enabled. Based on this it might be possible to further reduce the
overhead by also specializing the call itself.

As a drive-by-fix, port the fast context materialization optimization to
arm and arm64, that was previously only supported on x64 and ia32.

R=svenpanne@chromium.org

Committed: https://crrev.com/725cdc533cb4e31c042d32ce1979012b5bd99ced
Cr-Commit-Position: refs/heads/master@{#27686}

[Benedikt Meurer, 2015-04-09 06:57:29]

Hey Sven,

This is a trivial optimization, that avoids having to materialize the JSFunction
as constant (which requires a PropertyCell indirection if the JSFunction is in
new space, which happens quite often), but loads the JSFunction from the
activation record instead.

Gives speedup on recursive calls, i.e. in the towers benchmark. Please take a
look.

-- Benedikt

[Sven Panne, 2015-04-09 07:06:43]

The CQ bit was checked by svenpanne@chromium.org

[Sven Panne, 2015-04-09 07:06:43]

lgtm

[commit-bot: I haz the power, 2015-04-09 07:06:53]

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

[commit-bot: I haz the power, 2015-04-09 07:41:15]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-04-09 07:41:27]

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