Remove decision by Turbofan OSR to optimize on next call
When we OSR using Turbofan, we would set the function to be optimized on the next call, irrespective of the runtime profiler's previous decisions - such as compiling for baseline. It seems more prudent to always make these decisions in the runtime profiler where the data is available. Review-Url: https://codereview.chromium.org/2369043002 Cr-Commit-Position: refs/heads/master@{#39782}
Showing
Please
register
or
sign in
to comment