[turbofan] Mark JSStackCheck as no-write.

[turbofan] Mark JSStackCheck as no-write.

This is compatible with what Crankshaft does, and therefore should be
safe. The runtime doesn't perform any JavaScript-observable side
effects during the stack check.

R=jarin@chromium.org

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

[Jarin, 2016-07-04 12:36:31]

lgtm

[Benedikt Meurer, 2016-07-04 12:36:52]

The CQ bit was checked by bmeurer@chromium.org

[commit-bot: I haz the power, 2016-07-04 12:37:05]

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-04 12:55:41]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-07-04 12:56:10]

Description was changed from

==========
[turbofan] Mark JSStackCheck as no-write.

This is compatible with what Crankshaft does, and therefore should be
safe. The runtime doesn't perform any JavaScript-observable side
effects during the stack check.

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

to

==========
[turbofan] Mark JSStackCheck as no-write.

This is compatible with what Crankshaft does, and therefore should be
safe. The runtime doesn't perform any JavaScript-observable side
effects during the stack check.

R=jarin@chromium.org

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

[commit-bot: I haz the power, 2016-07-04 12:56:10]

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