• mstarzinger's avatar
    [compiler] Fix confusion about OSR BailoutId semantics. · b848716c
    mstarzinger authored
    The semantics of the {BailoutId} representing an OSR entry point is
    different between the interpreter and the full code generator. These
    semantics are hard-coded in various graph builders. We need to ensure
    that the correct graph builder is chosen for OSR compilations.
    
    R=rmcilroy@chromium.org
    TEST=mjsunit/regress/regress-5380
    BUG=v8:5380
    
    Review-Url: https://codereview.chromium.org/2341663002
    Cr-Commit-Position: refs/heads/master@{#39444}
    b848716c
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...