PPC/s390: [turbofan] Correct lazy deopt by {JSCreate} operation.

PPC/s390: [turbofan] Correct lazy deopt by {JSCreate} operation.

Port 6ee0b6cec6b83791af8d3a7e122f14e4eb376974

Original Commit Message:

    This adds support for deoptimizing into the JSConstructStub after the
    receiver instantiation but before the actual constructor invocation.
    Such a deoptimization point is needed for cases where instantiation
    might be observed (e.g. when new.target is a proxy) and hence might
    trigger a deopt.

    We use this new deoptimization point for the "after" frame-state the
    inliner attaches to {JSCreate} nodes being inserted when constructor
    calls are being inlined.

R=mstarzinger@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com, michael_dawson@ca.ibm.com
BUG=v8:5638
LOG=N

Review-Url: https://codereview.chromium.org/2690213002
Cr-Commit-Position: refs/heads/master@{#43171}
Committed: https://chromium.googlesource.com/v8/v8/+/2703b06e6f3e6a1bab4ab5c5e90034472d02423d

[JaideepBajwa, 2017-02-13 21:31:02]

ptal

[john.yan, 2017-02-13 22:18:10]

lgtm

[JaideepBajwa, 2017-02-13 22:18:25]

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

[commit-bot: I haz the power, 2017-02-13 22:18:32]

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

[commit-bot: I haz the power, 2017-02-13 22:42:51]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1487024305919350, "parent_rev":
"a386eb4f04b258a9e76cd0249146b4c856ee1cd6", "commit_rev":
"2703b06e6f3e6a1bab4ab5c5e90034472d02423d"}

[commit-bot: I haz the power, 2017-02-13 22:42:57]

Description was changed from

==========
PPC/s390: [turbofan] Correct lazy deopt by {JSCreate} operation.

Port 6ee0b6cec6b83791af8d3a7e122f14e4eb376974

Original Commit Message:

    This adds support for deoptimizing into the JSConstructStub after the
    receiver instantiation but before the actual constructor invocation.
    Such a deoptimization point is needed for cases where instantiation
    might be observed (e.g. when new.target is a proxy) and hence might
    trigger a deopt.

    We use this new deoptimization point for the "after" frame-state the
    inliner attaches to {JSCreate} nodes being inserted when constructor
    calls are being inlined.

R=mstarzinger@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com,
michael_dawson@ca.ibm.com
BUG=v8:5638
LOG=N
==========

to

==========
PPC/s390: [turbofan] Correct lazy deopt by {JSCreate} operation.

Port 6ee0b6cec6b83791af8d3a7e122f14e4eb376974

Original Commit Message:

    This adds support for deoptimizing into the JSConstructStub after the
    receiver instantiation but before the actual constructor invocation.
    Such a deoptimization point is needed for cases where instantiation
    might be observed (e.g. when new.target is a proxy) and hence might
    trigger a deopt.

    We use this new deoptimization point for the "after" frame-state the
    inliner attaches to {JSCreate} nodes being inserted when constructor
    calls are being inlined.

R=mstarzinger@chromium.org, joransiu@ca.ibm.com, jyan@ca.ibm.com,
michael_dawson@ca.ibm.com
BUG=v8:5638
LOG=N

Review-Url: https://codereview.chromium.org/2690213002
Cr-Commit-Position: refs/heads/master@{#43171}
Committed:
https://chromium.googlesource.com/v8/v8/+/2703b06e6f3e6a1bab4ab5c5e90034472d0...
==========

[commit-bot: I haz the power, 2017-02-13 22:42:58]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/v8/v8/+/2703b06e6f3e6a1bab4ab5c5e90034472d0...