Fix %OptimizeFunctionOnNextCall wrt concurrent compilation.
authoryangguo@chromium.org <yangguo@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Wed, 5 Feb 2014 12:19:29 +0000 (12:19 +0000)
committeryangguo@chromium.org <yangguo@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Wed, 5 Feb 2014 12:19:29 +0000 (12:19 +0000)
commit5fadbd9e2fd1f000b1355ef280bfd5a69c18923a
tree8da1db2db3dd1c07cfbadc22b9444dc21d75fc81
parent736e0a05f8e576464851c468620fa9b892adfd50
Fix %OptimizeFunctionOnNextCall wrt concurrent compilation.

If a function is marked or queued for concurrent compilation,
%OptimizeFunctionOnNextCall becomes a no-op. That can be wrong
if concurrent recompilation does not complete at the time we
expect the function to have been optimized.

R=hpayer@chromium.org

Review URL: https://codereview.chromium.org/151343006

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@19100 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
src/runtime.cc