• mstarzinger's avatar
    [turbofan] Advance bytecode offset after lazy deopt. · 93c65952
    mstarzinger authored
    This changes {FrameState} nodes modeling "after" states to use bytecode
    offsets pointing to the deoptimizing bytecode. This is in sync with the
    normal execution, as the bytecode offset is advanced after operations
    complete in regular bytecode handlers.
    
    The change is necessary to ensure lazy deoptimized frames contain an
    accurate bytecode offset while they are on the stack. Such frames can be
    inspected by various stack walks. The continuation builtin will advance
    the bytecode offset upon return.
    
    R=jarin@chromium.org
    TEST=mjsunit/regress/regress-crbug-660379
    BUG=chromium:660379
    
    Review-Url: https://codereview.chromium.org/2487173002
    Cr-Commit-Position: refs/heads/master@{#40887}
    93c65952
builtins-ia32.cc 112 KB