[turbofan] Remove Float32 truncation.

[turbofan] Remove Float32 truncation.

R=jarin@chromium.org
BUG=

Committed: https://crrev.com/26307c76c3193275e387a142b5d49ae7620e2e91
Cr-Commit-Position: refs/heads/master@{#40266}

[mvstanton, 2016-10-12 14:08:50]

The CQ bit was checked by mvstanton@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-10-12 14:08:54]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[mvstanton, 2016-10-12 14:09:37]

Hi Jaro,
Does it make sense to return a non-truncating Float32 UseInfo?
Thanks for the look!
--Mike

[commit-bot: I haz the power, 2016-10-12 14:32:12]

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

[commit-bot: I haz the power, 2016-10-12 14:32:13]

Dry run: This issue passed the CQ dry run.

[Jarin, 2016-10-12 18:04:02]

lgtm

https://codereview.chromium.org/2407153007/diff/1/src/compiler/representation...
File src/compiler/representation-change.h (right):

https://codereview.chromium.org/2407153007/diff/1/src/compiler/representation...
src/compiler/representation-change.h:136: return
UseInfo(MachineRepresentation::kFloat32, Truncation::Any());
It might be better to say kFloat64; otherwise float32 use from of
float64-or-undefined value (such as read from a double or float typed array)
will force tagged representation.

[mvstanton, 2016-10-13 13:25:37]

The CQ bit was checked by mvstanton@chromium.org

[commit-bot: I haz the power, 2016-10-13 13:25:44]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[mvstanton, 2016-10-13 13:25:48]

Thanks Jaro, landing...

https://codereview.chromium.org/2407153007/diff/1/src/compiler/representation...
File src/compiler/representation-change.h (right):

https://codereview.chromium.org/2407153007/diff/1/src/compiler/representation...
src/compiler/representation-change.h:136: return
UseInfo(MachineRepresentation::kFloat32, Truncation::Any());
On 2016/10/12 18:04:01, Jarin wrote:
> It might be better to say kFloat64; otherwise float32 use from of
> float64-or-undefined value (such as read from a double or float typed array)
> will force tagged representation.

Per our offline discussion, I'll go ahead and land it like this. Looks like
asm.js depends on this behavior.

[commit-bot: I haz the power, 2016-10-13 13:38:04]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-10-13 13:38:34]

Description was changed from

==========
[turbofan] Remove Float32 truncation.

R=jarin@chromium.org
BUG=
==========

to

==========
[turbofan] Remove Float32 truncation.

R=jarin@chromium.org
BUG=

Committed: https://crrev.com/26307c76c3193275e387a142b5d49ae7620e2e91
Cr-Commit-Position: refs/heads/master@{#40266}
==========

[commit-bot: I haz the power, 2016-10-13 13:38:35]

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