[crankshaft] Re-add kAllowUndefinedAsNaN flag for bitwise binary ops

[crankshaft] Re-add kAllowUndefinedAsNaN flag for bitwise binary ops

It appears to have been dropped accidentally as part of 1150092b29's
removal of strong mode for binary ops.

Committed: https://crrev.com/8c0ee440c1df1c759c579d9336ff681279ae9568
Cr-Commit-Position: refs/heads/master@{#37229}

[adamk, 2016-06-22 20:02:00]

adamk@chromium.org changed reviewers:
+ bmeurer@chromium.org, mstarzinger@chromium.org

[adamk, 2016-06-22 20:02:01]

Found this while doing some archeology on hydrogen.cc. See
https://codereview.chromium.org/1693833002/diff/100001/src/crankshaft/hydroge...
for how the code got like this.

[Benedikt Meurer, 2016-06-23 03:49:39]

LGTM, although I don't think it matters since the bitwise operations are
truncating-to-int32, which is even stronger.

[adamk, 2016-06-23 21:03:33]

The CQ bit was checked by adamk@chromium.org

[commit-bot: I haz the power, 2016-06-23 21:03:40]

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

[commit-bot: I haz the power, 2016-06-23 21:35:31]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-06-23 21:36:26]

Description was changed from

==========
[crankshaft] Re-add kAllowUndefinedAsNaN flag for bitwise binary ops

It appears to have been dropped accidentally as part of 1150092b29's
removal of strong mode for binary ops.
==========

to

==========
[crankshaft] Re-add kAllowUndefinedAsNaN flag for bitwise binary ops

It appears to have been dropped accidentally as part of 1150092b29's
removal of strong mode for binary ops.

Committed: https://crrev.com/8c0ee440c1df1c759c579d9336ff681279ae9568
Cr-Commit-Position: refs/heads/master@{#37229}
==========

[commit-bot: I haz the power, 2016-06-23 21:36:27]

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