Make it easier to test OSR with %OptimizeOsr() runtime call.

Make it easier to test OSR with %OptimizeOsr() runtime call.

This call triggers OSR for the current function. And also allows explicitly testing OSR on the top-level code.

R=mstarzinger@chromium.org
BUG=

Committed: https://crrev.com/4c302ca2906874e8efe4f1185fa1fa688ea714d6
Cr-Commit-Position: refs/heads/master@{#26523}

[titzer, 2015-02-09 10:53:31]

The CQ bit was checked by titzer@chromium.org

[commit-bot: I haz the power, 2015-02-09 10:54:28]

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

[commit-bot: I haz the power, 2015-02-09 10:54:29]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-02-09 10:54:32]

No LGTM from a valid reviewer yet. Only full committers are accepted.
Even if an LGTM may have been provided, it was from a non-committer,
_not_ a full super star committer.
See http://www.chromium.org/getting-involved/become-a-committer
Note that this has nothing to do with OWNERS files.

[Michael Starzinger, 2015-02-09 12:11:07]

LGTM.

https://codereview.chromium.org/906243002/diff/20001/src/runtime/runtime-test.cc
File src/runtime/runtime-test.cc (right):

https://codereview.chromium.org/906243002/diff/20001/src/runtime/runtime-test...
src/runtime/runtime-test.cc:85: HandleScope scope(isolate);
nit: Please place the HandleScope first before the runtime assert ... that way
it's easy to see that all runtime-functions either have a HandleScope or a
SealHandleScope on top.

https://codereview.chromium.org/906243002/diff/20001/src/runtime/runtime.h
File src/runtime/runtime.h (right):

https://codereview.chromium.org/906243002/diff/20001/src/runtime/runtime.h#ne...
src/runtime/runtime.h:69: F(OptimizeOsr, 0, 1)                                  
  \
As dicussed offline: I still think OptimizeViaOsr or something like that would
be a better name. But I am fine with this short version as well.

[titzer, 2015-02-09 12:15:06]

New patchsets have been uploaded after l-g-t-m from mstarzinger@chromium.org

[titzer, 2015-02-09 12:16:02]

https://codereview.chromium.org/906243002/diff/20001/src/runtime/runtime-test.cc
File src/runtime/runtime-test.cc (right):

https://codereview.chromium.org/906243002/diff/20001/src/runtime/runtime-test...
src/runtime/runtime-test.cc:85: HandleScope scope(isolate);
On 2015/02/09 12:11:06, Michael Starzinger wrote:
> nit: Please place the HandleScope first before the runtime assert ... that way
> it's easy to see that all runtime-functions either have a HandleScope or a
> SealHandleScope on top.

Done.

https://codereview.chromium.org/906243002/diff/20001/src/runtime/runtime.h
File src/runtime/runtime.h (right):

https://codereview.chromium.org/906243002/diff/20001/src/runtime/runtime.h#ne...
src/runtime/runtime.h:69: F(OptimizeOsr, 0, 1)                                  
  \
On 2015/02/09 12:11:06, Michael Starzinger wrote:
> As dicussed offline: I still think OptimizeViaOsr or something like that would
> be a better name. But I am fine with this short version as well.

I like short. I was just going to make it "Osr" but that seems too C-hacker
style ;).

[titzer, 2015-02-09 12:16:07]

The CQ bit was checked by titzer@chromium.org

[commit-bot: I haz the power, 2015-02-09 12:16:48]

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

[commit-bot: I haz the power, 2015-02-09 12:47:38]

Committed patchset #3 (id:40001)

[commit-bot: I haz the power, 2015-02-09 12:47:52]

Patchset 3 (id:??) landed as
https://crrev.com/4c302ca2906874e8efe4f1185fa1fa688ea714d6
Cr-Commit-Position: refs/heads/master@{#26523}