• 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...
cctest Loading commit data...
common Loading commit data...
debugger Loading commit data...
fuzzer Loading commit data...
inspector 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...