• rmcilroy's avatar
    [Interpreter] Move jump processing to bytecode array writer. · de9d1d8b
    rmcilroy authored
    This moves processing of jumps out of bytecode array builder and into
    bytecode array writer. This simplifies the pipeline by avoiding having
    to flush for offset and patch up offsets in bytecode array builder based
    on what was emitted by the bytecode array writer.
    
    This also enables future refactorings to add dead code elimination back
    into the pipeline, and move processing of scalable operand sizes to the
    end of the pipeline (in the bytecode array writer) rather than having to
    deal with scalable operand types throughout pipeline.
    
    BUG=v8:4280,chromium:616064
    
    Review-Url: https://codereview.chromium.org/2035813002
    Cr-Commit-Position: refs/heads/master@{#36716}
    de9d1d8b
Name
Last commit
Last update
..
benchmarks Loading commit data...
cctest Loading commit data...
fuzzer 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...
ignition.gyp Loading commit data...
ignition.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...