Make compiler more acceptive wrt Isolate::use_crankshaft.

Make compiler more acceptive wrt Isolate::use_crankshaft.

This allows using %OptimizeFunctionOnNextCall and friends even when
Crankshaft is disabled. Note that this should only affect code paths
that are not relevant to performance. By now we have a single bailout
point in place within OptimizedCompileJob::CreateGraph that ensures
Crankshaft is only used when enabled and supported.

R=titzer@chromium.org

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

[titzer, 2015-03-23 14:13:04]

On 2015/03/23 14:09:56, Michael Starzinger wrote:

LGTM YUMM

[Michael Starzinger, 2015-03-23 14:18:42]

The CQ bit was checked by mstarzinger@chromium.org

[commit-bot: I haz the power, 2015-03-23 14:18:55]

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

[commit-bot: I haz the power, 2015-03-23 14:25:50]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-03-23 14:25:58]

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