• mstarzinger's avatar
    [interpreter] Switch profiler to use frames for OSR. · 685210ec
    mstarzinger authored
    This switches the interface of the runtime profiler to use frames as
    opposed to functions for performing on-stack replacement. Requests for
    such replacements need to target a specific frame. This will enable us
    to activate bytecode as well as baseline code for the same function.
    
    The existing %OptimizeOsr runtime function also had to adapted and now
    takes an optional stack depth to target a specific stack frame.
    
    R=bmeurer@chromium.org
    BUG=v8:4764
    
    Review-Url: https://codereview.chromium.org/2230783004
    Cr-Commit-Position: refs/heads/master@{#38548}
    685210ec
Name
Last commit
Last update
..
benchmarks Loading commit data...
cctest Loading commit data...
fuzzer Loading commit data...
inspector_protocol_parser_test Loading commit data...
intl Loading commit data...
js-perf-test Loading commit data...
memory Loading commit data...
message Loading commit data...
mjsunit Loading commit data...
mozilla Loading commit data...
preparser Loading commit data...
promises-aplus Loading commit data...
simdjs Loading commit data...
test262 Loading commit data...
unittests Loading commit data...
webkit Loading commit data...
BUILD.gn Loading commit data...
bot_default.gyp Loading commit data...
bot_default.isolate Loading commit data...
default.gyp Loading commit data...
default.isolate Loading commit data...
optimize_for_size.gyp Loading commit data...
optimize_for_size.isolate Loading commit data...
perf.gyp Loading commit data...
perf.isolate Loading commit data...