[wasm] Fixed float-to-int conversion tests.

[wasm] Fixed float-to-int conversion tests.

*) For all tests the input validation was incorrect, i.e. some values
were considered invalid although they were valid. The problem was that
values which are outside int range can get in range through truncation.

*) Removed an assertion in the x64 code generation of
TruncateFloat64ToUint32 which trapped on negative inputs.

*) Introduced a new TF operator TruncateFloat32ToUint32 which does
the same as ChangeFloat32ToUint32 but does not trap on negative inputs.

R=titzer@chromium.org

Committed: https://crrev.com/ac7f0e2b6183839e55136647f81d6c01ac1b93af
Cr-Commit-Position: refs/heads/master@{#35176}

[titzer, 2016-03-31 09:02:55]

lgtm

https://codereview.chromium.org/1843983002/diff/1/src/compiler/x64/instructio...
File src/compiler/x64/instruction-selector-x64.cc (right):

https://codereview.chromium.org/1843983002/diff/1/src/compiler/x64/instructio...
src/compiler/x64/instruction-selector-x64.cc:898: Emit(kSSEFloat64ToUint32 |
MiscField::encode(true), g.DefineAsRegister(node),
Pass 1 here instead of {true}, because this Misc field encodes an int.

[ahaas, 2016-03-31 17:34:55]

On 2016/03/31 at 09:02:55, titzer wrote:
> lgtm
> 
>
https://codereview.chromium.org/1843983002/diff/1/src/compiler/x64/instructio...
> File src/compiler/x64/instruction-selector-x64.cc (right):
> 
>
https://codereview.chromium.org/1843983002/diff/1/src/compiler/x64/instructio...
> src/compiler/x64/instruction-selector-x64.cc:898: Emit(kSSEFloat64ToUint32 |
MiscField::encode(true), g.DefineAsRegister(node),
> Pass 1 here instead of {true}, because this Misc field encodes an int.

Done.

[ahaas, 2016-03-31 17:34:59]

The CQ bit was checked by ahaas@chromium.org

[ahaas, 2016-03-31 17:34:59]

The patchset sent to the CQ was uploaded after l-g-t-m from titzer@chromium.org
Link to the patchset: https://codereview.chromium.org/1843983002/#ps20001
(title: " ")

[commit-bot: I haz the power, 2016-03-31 17:35:05]

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

[commit-bot: I haz the power, 2016-03-31 18:38:21]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2016-03-31 18:38:42]

Description was changed from

==========
[wasm] Fixed float-to-int conversion tests.

*) For all tests the input validation was incorrect, i.e. some values
were considered invalid although they were valid. The problem was that
values which are outside int range can get in range through truncation.

*) Removed an assertion in the x64 code generation of
TruncateFloat64ToUint32 which trapped on negative inputs.

*) Introduced a new TF operator TruncateFloat32ToUint32 which does
the same as ChangeFloat32ToUint32 but does not trap on negative inputs.

R=titzer@chromium.org
==========

to

==========
[wasm] Fixed float-to-int conversion tests.

*) For all tests the input validation was incorrect, i.e. some values
were considered invalid although they were valid. The problem was that
values which are outside int range can get in range through truncation.

*) Removed an assertion in the x64 code generation of
TruncateFloat64ToUint32 which trapped on negative inputs.

*) Introduced a new TF operator TruncateFloat32ToUint32 which does
the same as ChangeFloat32ToUint32 but does not trap on negative inputs.

R=titzer@chromium.org

Committed: https://crrev.com/ac7f0e2b6183839e55136647f81d6c01ac1b93af
Cr-Commit-Position: refs/heads/master@{#35176}
==========

[commit-bot: I haz the power, 2016-03-31 18:38:43]

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