PPC/s390: [turbofan] Advance bytecode offset after lazy deopt.

PPC/s390: [turbofan] Advance bytecode offset after lazy deopt.

Port 93c65952009a611b840142e63237c58c7267bfd1

Original commit message:

    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=mstarzinger@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com
BUG=
LOG=N

Committed: https://crrev.com/a5467aae1ec7427a67b3cd8a0635c1f7ff62e25a
Cr-Commit-Position: refs/heads/master@{#40898}

[JaideepBajwa, 2016-11-10 14:16:02]

ptal

[john.yan, 2016-11-10 14:18:32]

lgtm

[JaideepBajwa, 2016-11-10 14:20:39]

The CQ bit was checked by bjaideep@ca.ibm.com

[commit-bot: I haz the power, 2016-11-10 14:20:42]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[Michael Starzinger, 2016-11-10 14:26:09]

LGTM. Thanks!

[commit-bot: I haz the power, 2016-11-10 14:41:22]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-11-17 22:29:26]

Description was changed from

==========
PPC/s390: [turbofan] Advance bytecode offset after lazy deopt.

Port 93c65952009a611b840142e63237c58c7267bfd1

Original commit message:

    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=mstarzinger@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com,
michael_dawson@ca.ibm.com
BUG=
LOG=N
==========

to

==========
PPC/s390: [turbofan] Advance bytecode offset after lazy deopt.

Port 93c65952009a611b840142e63237c58c7267bfd1

Original commit message:

    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=mstarzinger@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com,
michael_dawson@ca.ibm.com
BUG=
LOG=N

Committed: https://crrev.com/a5467aae1ec7427a67b3cd8a0635c1f7ff62e25a
Cr-Commit-Position: refs/heads/master@{#40898}
==========

[commit-bot: I haz the power, 2016-11-17 22:29:27]

Patchset 1 (id:??) landed as
https://crrev.com/a5467aae1ec7427a67b3cd8a0635c1f7ff62e25a
Cr-Commit-Position: refs/heads/master@{#40898}