• Dan Elphick's avatar
    [interpreter] Always put bytecode handlers in builtins table · daa296b5
    Dan Elphick authored
    This always creates the bytecode handlers as part of the builtins table
    regardless of the V8_EMBEDDED_BYTECODE_HANDLERS definition.
    
    Lazy deserialization of bytecode handlers is enabled for this flow by
    moving the three lazy bytecode deserializers from the strong roots into
    the builtins table (ensuring that they not marked lazy themselves).
    
    To simplify lazy deserialization, the illegal bytecode handler is made
    non-lazy so that GetAndMaybeDeserializeBytecodeHandler doesn't to know
    about it.
    
    Since the bytecode handlers are now always part of the builtins table,
    many bytecode specific methods are removed, including logging and in
    BuiltinsSerializer and BuiltinsDeserializer.
    
    Removes setup-interpreter.h, setup-interpreter-internal.cc and
    builtin-snapshot-utils.*.
    
    Change-Id: Ie421aa897a04f7b3bcb964c476eb7ab149388d53
    Reviewed-on: https://chromium-review.googlesource.com/1220046Reviewed-by: 's avatarHannes Payer <hpayer@chromium.org>
    Reviewed-by: 's avatarJakob Gruber <jgruber@chromium.org>
    Reviewed-by: 's avatarRoss McIlroy <rmcilroy@chromium.org>
    Commit-Queue: Dan Elphick <delphick@chromium.org>
    Cr-Commit-Position: refs/heads/master@{#56063}
    daa296b5
setup-isolate-for-tests.cc 588 Bytes