• mstarzinger's avatar
    [interpreter] Fix profiler when hitting OSR frame. · f00b42ae
    mstarzinger authored
    This fixes the runtime profiler to no longer assume that seeing an
    optimized frame on the stack implies the underlying function is not
    being interpreted when entered normally. This no longer holds with code
    generated for OSR directly from bytecode (not installed on function).
    
    R=rmcilroy@chromium.org
    TEST=mjsunit/regress/regress-crbug-632800
    BUG=chromium:632800
    
    Review-Url: https://codereview.chromium.org/2208603005
    Cr-Commit-Position: refs/heads/master@{#38360}
    f00b42ae
Name
Last commit
Last update
benchmarks Loading commit data...
build_overrides Loading commit data...
docs Loading commit data...
gni Loading commit data...
gypfiles Loading commit data...
include Loading commit data...
infra Loading commit data...
samples Loading commit data...
src Loading commit data...
test Loading commit data...
testing Loading commit data...
third_party/binutils Loading commit data...
tools Loading commit data...
.clang-format Loading commit data...
.gitignore Loading commit data...
.gn Loading commit data...
.ycm_extra_conf.py Loading commit data...
AUTHORS Loading commit data...
BUILD.gn Loading commit data...
CODE_OF_CONDUCT.md Loading commit data...
ChangeLog Loading commit data...
DEPS Loading commit data...
LICENSE Loading commit data...
LICENSE.fdlibm Loading commit data...
LICENSE.strongtalk Loading commit data...
LICENSE.v8 Loading commit data...
LICENSE.valgrind Loading commit data...
Makefile Loading commit data...
Makefile.android Loading commit data...
OWNERS Loading commit data...
PRESUBMIT.py Loading commit data...
README.md Loading commit data...
WATCHLISTS Loading commit data...
codereview.settings Loading commit data...
snapshot_toolchain.gni Loading commit data...