[turbofan] Introduce CheckUnless.

[turbofan] Introduce CheckUnless.

Similarly to CheckIf, CheckUnless is a deoptimization without a specific
frame state. A frame state is assigned during effect-control linearization
(and CheckUnless is turned into DeoptimizeUnless).

At the moment, the new operator is only used at one place in native context
specialization, but we should use it everywhere. The advantage of
CHeckUnless is that it avoids non-truncating uses of values by frame
states. This particular change is aimed at Octane's crypto, where this
enables to turn one NumberMultiply into Int32Mul, and thus improve
the score by more than 10% (it also needs minus zero truncation and
typing to be improved, but those CLs are already in flight).

BUG=v8:4470
R=bmeurer@chromium.org

Committed: https://crrev.com/85fde59d538e0dcaf461108086c2f7cf904f567a
Cr-Commit-Position: refs/heads/master@{#37085}

[Jarin, 2016-06-19 19:05:45]

jarin@chromium.org changed reviewers:
+ bmeurer@chromium.org

[Jarin, 2016-06-19 19:05:45]

Could you take a look, please?

[Benedikt Meurer, 2016-06-20 03:44:10]

Description was changed from

==========
[turbofan] Introduce CheckUnless.

Similarly to CheckIf, CheckUnless is a deoptimization without a specific
frame state. A frame state is assigned during effect-control linearization
(and CheckUnless is turned into DeoptimizeUnless).

At the moment, the new operator is only used at one place in native context
specialization, but we should use it everywhere. The advantage of
CHeckUnless is that it avoids non-truncating uses of values by frame
states. This particular change is aimed at Octane's crypto, where this
enables to turn one NumberMultiply into Int32Mul, and thus improve
the score by more than 10% (it also needs minus zero truncation and
typing to be improved, but those CLs are already in flight).
==========

to

==========
[turbofan] Introduce CheckUnless.

Similarly to CheckIf, CheckUnless is a deoptimization without a specific
frame state. A frame state is assigned during effect-control linearization
(and CheckUnless is turned into DeoptimizeUnless).

At the moment, the new operator is only used at one place in native context
specialization, but we should use it everywhere. The advantage of
CHeckUnless is that it avoids non-truncating uses of values by frame
states. This particular change is aimed at Octane's crypto, where this
enables to turn one NumberMultiply into Int32Mul, and thus improve
the score by more than 10% (it also needs minus zero truncation and
typing to be improved, but those CLs are already in flight).

BUG=v8:4470
R=bmeurer@chromium.org
==========

[Benedikt Meurer, 2016-06-20 03:44:47]

The CQ bit was checked by bmeurer@chromium.org

[Benedikt Meurer, 2016-06-20 03:44:48]

lgtm

[commit-bot: I haz the power, 2016-06-20 03:44:58]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/2080113002/1

[commit-bot: I haz the power, 2016-06-20 03:46:39]

Description was changed from

==========
[turbofan] Introduce CheckUnless.

Similarly to CheckIf, CheckUnless is a deoptimization without a specific
frame state. A frame state is assigned during effect-control linearization
(and CheckUnless is turned into DeoptimizeUnless).

At the moment, the new operator is only used at one place in native context
specialization, but we should use it everywhere. The advantage of
CHeckUnless is that it avoids non-truncating uses of values by frame
states. This particular change is aimed at Octane's crypto, where this
enables to turn one NumberMultiply into Int32Mul, and thus improve
the score by more than 10% (it also needs minus zero truncation and
typing to be improved, but those CLs are already in flight).

BUG=v8:4470
R=bmeurer@chromium.org
==========

to

==========
[turbofan] Introduce CheckUnless.

Similarly to CheckIf, CheckUnless is a deoptimization without a specific
frame state. A frame state is assigned during effect-control linearization
(and CheckUnless is turned into DeoptimizeUnless).

At the moment, the new operator is only used at one place in native context
specialization, but we should use it everywhere. The advantage of
CHeckUnless is that it avoids non-truncating uses of values by frame
states. This particular change is aimed at Octane's crypto, where this
enables to turn one NumberMultiply into Int32Mul, and thus improve
the score by more than 10% (it also needs minus zero truncation and
typing to be improved, but those CLs are already in flight).

BUG=v8:4470
R=bmeurer@chromium.org
==========

[commit-bot: I haz the power, 2016-06-20 03:46:40]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-06-20 03:48:30]

Description was changed from

==========
[turbofan] Introduce CheckUnless.

Similarly to CheckIf, CheckUnless is a deoptimization without a specific
frame state. A frame state is assigned during effect-control linearization
(and CheckUnless is turned into DeoptimizeUnless).

At the moment, the new operator is only used at one place in native context
specialization, but we should use it everywhere. The advantage of
CHeckUnless is that it avoids non-truncating uses of values by frame
states. This particular change is aimed at Octane's crypto, where this
enables to turn one NumberMultiply into Int32Mul, and thus improve
the score by more than 10% (it also needs minus zero truncation and
typing to be improved, but those CLs are already in flight).

BUG=v8:4470
R=bmeurer@chromium.org
==========

to

==========
[turbofan] Introduce CheckUnless.

Similarly to CheckIf, CheckUnless is a deoptimization without a specific
frame state. A frame state is assigned during effect-control linearization
(and CheckUnless is turned into DeoptimizeUnless).

At the moment, the new operator is only used at one place in native context
specialization, but we should use it everywhere. The advantage of
CHeckUnless is that it avoids non-truncating uses of values by frame
states. This particular change is aimed at Octane's crypto, where this
enables to turn one NumberMultiply into Int32Mul, and thus improve
the score by more than 10% (it also needs minus zero truncation and
typing to be improved, but those CLs are already in flight).

BUG=v8:4470
R=bmeurer@chromium.org

Committed: https://crrev.com/85fde59d538e0dcaf461108086c2f7cf904f567a
Cr-Commit-Position: refs/heads/master@{#37085}
==========

[commit-bot: I haz the power, 2016-06-20 03:48:31]

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

[Michael Achenbach, 2016-06-20 07:40:27]

A revert of this CL (patchset #1 id:1) has been created in
https://codereview.chromium.org/2078333002/ by machenbach@chromium.org.

The reason for reverting is: [Sheriff] Speculative revert: Seems to lead to
devtools crashes:
https://build.chromium.org/p/client.v8.fyi/builders/V8-Blink%20Win/builds/5259.