Don't call FastNewFunctionContextStub if context is bigger than kMaxRegularHeapObjectSize.

Don't call FastNewFunctionContextStub if context is bigger than kMaxRegularHeapObjectSize.

CL https://codereview.chromium.org/2177273002 changed FastNewFunctionContextStub
to take a number of slots parameter and in-doing so removed the maximum slot
count for FastNewFunctionContextStub. This made it possible to create a
closure which is larger than kMaxRegularHeapObjectSize and so can't be
allocated by FastNewFunctionContextStub.

Reintroduce FastNewFunctionContextStub::kMaxSlots (but make the limit much
larger) to ensure we call the runtime for contexts which need to be
allocated in the LO space.

BUG=chromium:655573
Committed: https://crrev.com/381b5437b2bf48885f870c7276e2f5cb4e9f8a02
Cr-Commit-Position: refs/heads/master@{#40541}

[rmcilroy, 2016-10-24 12:14:57]

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

[commit-bot: I haz the power, 2016-10-24 12:15:07]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[rmcilroy, 2016-10-24 12:17:35]

Patchset #1 (id:1) has been deleted

[rmcilroy, 2016-10-24 12:17:40]

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

[commit-bot: I haz the power, 2016-10-24 12:17:48]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[rmcilroy, 2016-10-24 12:33:02]

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

[rmcilroy, 2016-10-24 12:33:02]

Benedkit PTAL, thanks.

[commit-bot: I haz the power, 2016-10-24 13:43:40]

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

[commit-bot: I haz the power, 2016-10-24 13:43:41]

Dry run: This issue passed the CQ dry run.

[Benedikt Meurer, 2016-10-24 17:02:30]

LGTM, thanks.

[rmcilroy, 2016-10-24 17:18:32]

The CQ bit was checked by rmcilroy@chromium.org

[commit-bot: I haz the power, 2016-10-24 17:18:43]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-10-24 17:22:49]

Committed patchset #1 (id:20001)

[commit-bot: I haz the power, 2016-11-17 22:11:27]

Description was changed from

==========
Don't call FastNewFunctionContextStub if context is bigger than
kMaxRegularHeapObjectSize.

CL https://codereview.chromium.org/2177273002 changed FastNewFunctionContextStub
to take a number of slots parameter and in-doing so removed the maximum slot
count for FastNewFunctionContextStub. This made it possible to create a
closure which is larger than kMaxRegularHeapObjectSize and so can't be
allocated by FastNewFunctionContextStub.

Reintroduce FastNewFunctionContextStub::kMaxSlots (but make the limit much
larger) to ensure we call the runtime for contexts which need to be
allocated in the LO space.

BUG=chromium:655573
==========

to

==========
Don't call FastNewFunctionContextStub if context is bigger than
kMaxRegularHeapObjectSize.

CL https://codereview.chromium.org/2177273002 changed FastNewFunctionContextStub
to take a number of slots parameter and in-doing so removed the maximum slot
count for FastNewFunctionContextStub. This made it possible to create a
closure which is larger than kMaxRegularHeapObjectSize and so can't be
allocated by FastNewFunctionContextStub.

Reintroduce FastNewFunctionContextStub::kMaxSlots (but make the limit much
larger) to ensure we call the runtime for contexts which need to be
allocated in the LO space.

BUG=chromium:655573

Committed: https://crrev.com/381b5437b2bf48885f870c7276e2f5cb4e9f8a02
Cr-Commit-Position: refs/heads/master@{#40541}
==========

[commit-bot: I haz the power, 2016-11-17 22:11:29]

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