[turbofan] Run JSGenericLowering as separate phase.

[turbofan] Run JSGenericLowering as separate phase.

This works around the problem that the lowering for JSStackCheck doesn't
play well with effect chain based state tracking, because it doesn't
report the correct changes (we will address this with a better handling
of stack checks soon).

It also allows us to run the EarlyOptimizationPhase concurrently, which
doesn't need to access the heap or generate code stubs.

R=jarin@chromium.org

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

[Benedikt Meurer, 2016-07-26 12:11:07]

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

[commit-bot: I haz the power, 2016-07-26 12:11:09]

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

[Jarin, 2016-07-26 12:12:36]

lgtm

[Benedikt Meurer, 2016-07-26 12:12:56]

The CQ bit was unchecked by bmeurer@chromium.org

[Benedikt Meurer, 2016-07-26 12:12:57]

The CQ bit was checked by bmeurer@chromium.org

[commit-bot: I haz the power, 2016-07-26 12:12:59]

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-07-26 12:32:53]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-07-26 12:36:14]

Description was changed from

==========
[turbofan] Run JSGenericLowering as separate phase.

This works around the problem that the lowering for JSStackCheck doesn't
play well with effect chain based state tracking, because it doesn't
report the correct changes (we will address this with a better handling
of stack checks soon).

It also allows us to run the EarlyOptimizationPhase concurrently, which
doesn't need to access the heap or generate code stubs.

R=jarin@chromium.org
==========

to

==========
[turbofan] Run JSGenericLowering as separate phase.

This works around the problem that the lowering for JSStackCheck doesn't
play well with effect chain based state tracking, because it doesn't
report the correct changes (we will address this with a better handling
of stack checks soon).

It also allows us to run the EarlyOptimizationPhase concurrently, which
doesn't need to access the heap or generate code stubs.

R=jarin@chromium.org

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

[commit-bot: I haz the power, 2016-07-26 12:36:14]

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