PPC/s390: [compiler] Drive optimizations with feedback vector (reland)

PPC/s390: [compiler] Drive optimizations with feedback vector (reland)

Port 24b7026d738415da9ccfb058ca0e27d133635beb

Original Commit Message:

    For interpreted functions, use the optimized code slot in the feedback
    vector to store an optimization marker (optimize/in optimization queue)
    rather than changing the JSFunction's code object. Then, adapt the
    self-healing mechanism to also dispatch based on this optimization
    marker. Similarly, replace SFI marking with optimization marker checks
    in CompileLazy.

    This allows JSFunctions to share optimization information (replacing
    shared function marking) without leaking this information across native
    contexts. Non I+TF functions (asm.js or --no-turbo) use a
    CheckOptimizationMarker shim which generalises the old
    CompileOptimized/InOptimizationQueue builtins and also checks the same
    optimization marker as CompileLazy and InterpreterEntryTrampoline.

    This is a reland of https://chromium-review.googlesource.com/c/509716

R=leszeks@chromium.org, joransiu@ca.ibm.com, bjaideep@ca.ibm.com, michael_dawson@ca.ibm.com
BUG=
LOG=N

Review-Url: https://codereview.chromium.org/2947903002
Cr-Commit-Position: refs/heads/master@{#46109}
Committed: https://chromium.googlesource.com/v8/v8/+/43f1461255d7073157d08f90d0d01493e9a862c0

[john.yan, 2017-06-21 19:38:10]

PTAL

[JaideepBajwa, 2017-06-21 19:39:15]

lgtm

[john.yan, 2017-06-21 19:48:52]

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

[commit-bot: I haz the power, 2017-06-21 19:48:57]

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-06-21 20:52:26]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-06-21 20:52:26]

Try jobs failed on following builders:
  v8_linux64_rel_ng on master.tryserver.v8 (JOB_FAILED,
http://build.chromium.org/p/tryserver.v8/builders/v8_linux64_rel_ng/builds/27938)
  v8_linux64_rel_ng_triggered on master.tryserver.v8 (JOB_FAILED,
http://build.chromium.org/p/tryserver.v8/builders/v8_linux64_rel_ng_triggered...)
  v8_linux_nodcheck_rel_ng on master.tryserver.v8 (JOB_FAILED,
http://build.chromium.org/p/tryserver.v8/builders/v8_linux_nodcheck_rel_ng/bu...)
  v8_linux_nodcheck_rel_ng_triggered on master.tryserver.v8 (JOB_FAILED,
http://build.chromium.org/p/tryserver.v8/builders/v8_linux_nodcheck_rel_ng_tr...)

[john.yan, 2017-06-21 21:04:45]

The CQ bit was unchecked by jyan@ca.ibm.com

[john.yan, 2017-06-21 21:04:50]

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

[commit-bot: I haz the power, 2017-06-21 21:04:56]

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-06-21 22:12:19]

CQ is committing da patch.

Bot data: {"patchset_id": 40001, "attempt_start_ts": 1498079090063020,
"parent_rev": "9f33191a041a3d7908d80db711c9a734d4440e2a", "commit_rev":
"43f1461255d7073157d08f90d0d01493e9a862c0"}

[commit-bot: I haz the power, 2017-06-21 22:12:25]

Description was changed from

==========
PPC/s390: [compiler] Drive optimizations with feedback vector (reland)

Port 24b7026d738415da9ccfb058ca0e27d133635beb

Original Commit Message:

    For interpreted functions, use the optimized code slot in the feedback
    vector to store an optimization marker (optimize/in optimization queue)
    rather than changing the JSFunction's code object. Then, adapt the
    self-healing mechanism to also dispatch based on this optimization
    marker. Similarly, replace SFI marking with optimization marker checks
    in CompileLazy.

    This allows JSFunctions to share optimization information (replacing
    shared function marking) without leaking this information across native
    contexts. Non I+TF functions (asm.js or --no-turbo) use a
    CheckOptimizationMarker shim which generalises the old
    CompileOptimized/InOptimizationQueue builtins and also checks the same
    optimization marker as CompileLazy and InterpreterEntryTrampoline.

    This is a reland of https://chromium-review.googlesource.com/c/509716

R=leszeks@chromium.org, joransiu@ca.ibm.com, bjaideep@ca.ibm.com,
michael_dawson@ca.ibm.com
BUG=
LOG=N
==========

to

==========
PPC/s390: [compiler] Drive optimizations with feedback vector (reland)

Port 24b7026d738415da9ccfb058ca0e27d133635beb

Original Commit Message:

    For interpreted functions, use the optimized code slot in the feedback
    vector to store an optimization marker (optimize/in optimization queue)
    rather than changing the JSFunction's code object. Then, adapt the
    self-healing mechanism to also dispatch based on this optimization
    marker. Similarly, replace SFI marking with optimization marker checks
    in CompileLazy.

    This allows JSFunctions to share optimization information (replacing
    shared function marking) without leaking this information across native
    contexts. Non I+TF functions (asm.js or --no-turbo) use a
    CheckOptimizationMarker shim which generalises the old
    CompileOptimized/InOptimizationQueue builtins and also checks the same
    optimization marker as CompileLazy and InterpreterEntryTrampoline.

    This is a reland of https://chromium-review.googlesource.com/c/509716

R=leszeks@chromium.org, joransiu@ca.ibm.com, bjaideep@ca.ibm.com,
michael_dawson@ca.ibm.com
BUG=
LOG=N

Review-Url: https://codereview.chromium.org/2947903002
Cr-Commit-Position: refs/heads/master@{#46109}
Committed:
https://chromium.googlesource.com/v8/v8/+/43f1461255d7073157d08f90d0d01493e9a...
==========

[commit-bot: I haz the power, 2017-06-21 22:12:26]

Committed patchset #3 (id:40001) as
https://chromium.googlesource.com/v8/v8/+/43f1461255d7073157d08f90d0d01493e9a...