• jgruber's avatar
    [builtins] Move DeserializeLazy to ASM · e67420cb
    jgruber authored
    There are two main reasons to move DeserializeLazy to ASM:
    
    1. We avoid complications around the distinction between Call/Construct
       cases by making sure relevant registers (e.g. new_target) remain
       unclobbered.
    
    2. We can avoid the tail-call through CodeFactory::Call/Construct by
       jumping directly to the deserialized code object.
    
    Bug: v8:6624
    Change-Id: Idef8fa73d804e16d510f62766c735d1891729b81
    Reviewed-on: https://chromium-review.googlesource.com/652472Reviewed-by: 's avatarMichael Starzinger <mstarzinger@chromium.org>
    Commit-Queue: Jakob Gruber <jgruber@chromium.org>
    Cr-Commit-Position: refs/heads/master@{#47876}
    e67420cb
builtins-definitions.h 87.9 KB