[wasm] min/max does not return signaling NaNs anymore.

[wasm] min/max does not return signaling NaNs anymore.

To avoid returning a signaling NaN the result is multiplied by 1.0.

R=titzer@chromium.org, binji@chromium.org

BUG=4733
LOG=Y

Committed: https://crrev.com/563539a3d65763d2608e88479cf5666a8b912234
Cr-Commit-Position: refs/heads/master@{#33783}

[ahaas, 2016-02-05 10:54:30]

On 2016/02/05 at 09:55:32, ahaas wrote:
> 

In the current implementation arm always returns a canonical NaN and not the
input NaN. I suspect that this breaks all NaN tests at the moment. I plan to
handle this in a separate CL after my vacation.

[titzer, 2016-02-05 13:12:14]

lgtm

[titzer, 2016-02-05 14:35:29]

The CQ bit was checked by titzer@chromium.org

[commit-bot: I haz the power, 2016-02-05 14:35:37]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1673583002/20001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1673583002/20001

[commit-bot: I haz the power, 2016-02-05 14:59:44]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2016-02-05 15:00:28]

Description was changed from

==========
[wasm] min/max does not return signaling NaNs anymore.

To avoid returning a signaling NaN the result is multiplied by 1.0.

R=titzer@chromium.org, binji@chromium.org

BUG=4733
LOG=Y
==========

to

==========
[wasm] min/max does not return signaling NaNs anymore.

To avoid returning a signaling NaN the result is multiplied by 1.0.

R=titzer@chromium.org, binji@chromium.org

BUG=4733
LOG=Y

Committed: https://crrev.com/563539a3d65763d2608e88479cf5666a8b912234
Cr-Commit-Position: refs/heads/master@{#33783}
==========

[commit-bot: I haz the power, 2016-02-05 15:00:29]

Patchset 2 (id:??) landed as
https://crrev.com/563539a3d65763d2608e88479cf5666a8b912234
Cr-Commit-Position: refs/heads/master@{#33783}