[turbofan] Fix handling of typed array loads in load elimination.

[turbofan] Fix handling of typed array loads in load elimination.

BUG=chromium:694088
Review-Url: https://codereview.chromium.org/2725593002
Cr-Commit-Position: refs/heads/master@{#43477}
Committed: https://chromium.googlesource.com/v8/v8/+/3c36aacc87f701fea0bb6976a4498dde61929a29

[Jarin, 2017-02-28 11:53:13]

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

[commit-bot: I haz the power, 2017-02-28 11:53:16]

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

[Jarin, 2017-02-28 11:58:25]

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

[Jarin, 2017-02-28 11:58:25]

Could you take a look, please?

[Benedikt Meurer, 2017-02-28 12:15:11]

lgtm

[Jarin, 2017-02-28 12:18:36]

The CQ bit was unchecked by jarin@chromium.org

[Jarin, 2017-02-28 12:18:38]

The CQ bit was checked by jarin@chromium.org

[commit-bot: I haz the power, 2017-02-28 12:18:43]

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

[commit-bot: I haz the power, 2017-02-28 12:20:20]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1488284318038940, "parent_rev":
"84ff6e4c1997b63c01e95504c31ee6c5504430d5", "commit_rev":
"3c36aacc87f701fea0bb6976a4498dde61929a29"}

[commit-bot: I haz the power, 2017-02-28 12:20:24]

Description was changed from

==========
[turbofan] Fix handling of typed array loads in load elimination.

BUG=chromium:694088
==========

to

==========
[turbofan] Fix handling of typed array loads in load elimination.

BUG=chromium:694088

Review-Url: https://codereview.chromium.org/2725593002
Cr-Commit-Position: refs/heads/master@{#43477}
Committed:
https://chromium.googlesource.com/v8/v8/+/3c36aacc87f701fea0bb6976a4498dde619...
==========

[commit-bot: I haz the power, 2017-02-28 12:20:25]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/v8/v8/+/3c36aacc87f701fea0bb6976a4498dde619...

[JaideepBajwa, 2017-03-01 21:52:17]

bjaideep@ca.ibm.com changed reviewers:
+ bjaideep@ca.ibm.com

[JaideepBajwa, 2017-03-01 21:52:19]

https://codereview.chromium.org/2725593002/diff/1/test/mjsunit/compiler/regre...
File test/mjsunit/compiler/regress-694088.js (right):

https://codereview.chromium.org/2725593002/diff/1/test/mjsunit/compiler/regre...
test/mjsunit/compiler/regress-694088.js:15: assertEquals(0, foo());
The testcase fails on Big Endian platforms, the behavior seems to be correct.
i32[0] comes out to be "0x3FF00000" on Big Endian.
What would be a suitable solution?
- validating differently based on endianess or
- disabling this testcase for Big endian or 
- have f64[0] to a something which yields same value in upper and lower 32bits.
For eg (might not be viable but this works)
f64[0] = 1.00000023818574845790863037109E0; assertEquals(0x3FF00000, foo());