• mvstanton's avatar
    Interpreter tester should accept metadata instead of a vector · d24ce605
    mvstanton authored
    The InterpreterTester class cobbles together a JSFunction from
    a manually created bytecode and feedback vector. However it's
    fragile against design changes in the way literal arrays and
    feedback vectors are handled. It's better to let it hand in
    a feedback vector metadata object, and allow the system to
    create the vector from that.
    
    BUG=v8:5456
    
    Review-Url: https://codereview.chromium.org/2652893010
    Cr-Commit-Position: refs/heads/master@{#42684}
    d24ce605
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 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...