Force eager compilation on closure scopes only

Force eager compilation on closure scopes only

In theory the flag could otherwise be set on a blockscope that might be finalized (removed) before PropagateScopeInfo can propagate the flag around. In that case we'd lose the flag.

BUG=v8:5209
Committed: https://crrev.com/d8bc37585364792baa2a80dbe23da58765b6ecaa
Cr-Commit-Position: refs/heads/master@{#38781}

[Toon Verwaest, 2016-08-22 11:48:09]

verwaest@chromium.org changed reviewers:
+ marja@chromium.org

[Toon Verwaest, 2016-08-22 11:48:09]

ptal

[marja, 2016-08-22 11:56:44]

lgtm

[Toon Verwaest, 2016-08-22 12:09:23]

The CQ bit was checked by verwaest@chromium.org

[commit-bot: I haz the power, 2016-08-22 12:09:30]

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-08-22 12:32:28]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-08-22 12:32:48]

Description was changed from

==========
Force eager compilation on closure scopes only

In theory the flag could otherwise be set on a blockscope that might be
finalized (removed) before PropagateScopeInfo can propagate the flag around. In
that case we'd lose the flag.

BUG=v8:5209
==========

to

==========
Force eager compilation on closure scopes only

In theory the flag could otherwise be set on a blockscope that might be
finalized (removed) before PropagateScopeInfo can propagate the flag around. In
that case we'd lose the flag.

BUG=v8:5209

Committed: https://crrev.com/d8bc37585364792baa2a80dbe23da58765b6ecaa
Cr-Commit-Position: refs/heads/master@{#38781}
==========

[commit-bot: I haz the power, 2016-08-22 12:32:49]

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