[turbofan] Use inline allocation for closures.

[turbofan] Use inline allocation for closures.

This changes closure creation to lower to inline allocations when
possible instead of going through the FastNewClosureStub. It allows us
to leverage all advantages of inline allocations on closures. Note that
it is only safe to embed the raw entry point of the compile lazy stub
into the code, because that stub is immortal and immovable.

R=mvstanton@chromium.org

Committed: https://crrev.com/43c7c76f1de26786884624df5435c766f4fe2fbe
Cr-Commit-Position: refs/heads/master@{#35499}

[Michael Starzinger, 2016-01-11 15:37:17]

Just a first prototype. Not planning to land any of this before we switched the
CompileLazy stub to be smarter and made the FastNewClosureStub dumber.

[Michael Starzinger, 2016-04-13 12:33:10]

This has just been upgraded from prototype to product. PTAL. :)

[mvstanton, 2016-04-14 12:41:34]

lgtm

[Michael Starzinger, 2016-04-14 14:55:55]

The CQ bit was checked by mstarzinger@chromium.org

[commit-bot: I haz the power, 2016-04-14 14:56:04]

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

[commit-bot: I haz the power, 2016-04-14 15:17:36]

Committed patchset #3 (id:40001)

[commit-bot: I haz the power, 2016-04-14 15:19:25]

Description was changed from

==========
[turbofan] Use inline allocation for closures.

This changes closure creation to lower to inline allocations when
possible instead of going through the FastNewClosureStub. It allows us
to leverage all advantages of inline allocations on closures. Note that
it is only safe to embed the raw entry point of the compile lazy stub
into the code, because that stub is immortal and immovable.

R=mvstanton@chromium.org
==========

to

==========
[turbofan] Use inline allocation for closures.

This changes closure creation to lower to inline allocations when
possible instead of going through the FastNewClosureStub. It allows us
to leverage all advantages of inline allocations on closures. Note that
it is only safe to embed the raw entry point of the compile lazy stub
into the code, because that stub is immortal and immovable.

R=mvstanton@chromium.org

Committed: https://crrev.com/43c7c76f1de26786884624df5435c766f4fe2fbe
Cr-Commit-Position: refs/heads/master@{#35499}
==========

[commit-bot: I haz the power, 2016-04-14 15:19:26]

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