• Peter Marshall's avatar
    [runtime] Remove the construct_stub field of the SFI · 63ecddc8
    Peter Marshall authored
    Don't dispatch based on the construct_stub field anymore. Rather than
    read it out and jump to the construct stub, we can switch on the
    builtin_id.
    
    Builtins will always have builtin_id as a Smi, so this signals we need
    to jump to JSBuiltinsConstructStub. The only exception is for uncompiled
    functions, which will have kCompileLazy as the builtin_id, but need to
    jump to the generic stub instead.
    
    API function calls will have a FunctionTemplateInfo in the SFI
    function_data field, and need to go to the builtins stub as well.
    
    The final case is everything else, which should go to the generic stub.
    
    Bug: v8:7503
    Change-Id: I14790a5f9784dc0d940bf10a05f5310026e1d482
    Reviewed-on: https://chromium-review.googlesource.com/980941Reviewed-by: 's avatarLeszek Swirski <leszeks@chromium.org>
    Reviewed-by: 's avatarBenedikt Meurer <bmeurer@chromium.org>
    Commit-Queue: Peter Marshall <petermarshall@chromium.org>
    Cr-Commit-Position: refs/heads/master@{#52345}
    63ecddc8
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...
mkgrokdump Loading commit data...
mozilla Loading commit data...
preparser Loading commit data...
test262 Loading commit data...
unittests Loading commit data...
wasm-spec-tests Loading commit data...
webkit Loading commit data...
BUILD.gn Loading commit data...