[turbofan] Deprecate CompilationInfo::has_scope predicate.

[turbofan] Deprecate CompilationInfo::has_scope predicate.

Now that we no longer compile stubs from JavaScript source, but have
other means of generating stubs using our optimizing compilers, we can
assume that scope analysis has happened whenever prologues are being
assembled.

R=bmeurer@chromium.org

Committed: https://crrev.com/105777a03665f8cbaa2cb2219d0e0eae8765b040
Cr-Commit-Position: refs/heads/master@{#35329}

[Benedikt Meurer, 2016-04-07 09:17:13]

lgtm

[Michael Starzinger, 2016-04-07 09:27:22]

The CQ bit was checked by mstarzinger@chromium.org

[commit-bot: I haz the power, 2016-04-07 09:27:26]

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

[commit-bot: I haz the power, 2016-04-07 09:52:23]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-04-07 09:54:21]

Description was changed from

==========
[turbofan] Deprecate CompilationInfo::has_scope predicate.

Now that we no longer compile stubs from JavaScript source, but have
other means of generating stubs using our optimizing compilers, we can
assume that scope analysis has happened whenever prologues are being
assembled.

R=bmeurer@chromium.org
==========

to

==========
[turbofan] Deprecate CompilationInfo::has_scope predicate.

Now that we no longer compile stubs from JavaScript source, but have
other means of generating stubs using our optimizing compilers, we can
assume that scope analysis has happened whenever prologues are being
assembled.

R=bmeurer@chromium.org

Committed: https://crrev.com/105777a03665f8cbaa2cb2219d0e0eae8765b040
Cr-Commit-Position: refs/heads/master@{#35329}
==========

[commit-bot: I haz the power, 2016-04-07 09:54:22]

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