• 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
..
bytecode_expectations Loading commit data...
bytecode-expectations-printer.cc Loading commit data...
bytecode-expectations-printer.h Loading commit data...
generate-bytecode-expectations.cc Loading commit data...
interpreter-tester.cc Loading commit data...
interpreter-tester.h Loading commit data...
test-bytecode-generator.cc Loading commit data...
test-interpreter-intrinsics.cc Loading commit data...
test-interpreter.cc Loading commit data...