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

test/mjsunit/compiler/regress-694088.js

Index: test/mjsunit/compiler/regress-694088.js
diff --git a/test/mjsunit/compiler/regress-694088.js b/test/mjsunit/compiler/regress-694088.js
new file mode 100644
index 0000000000000000000000000000000000000000..42817092a0cf14e3710d23fac973093c02224d8e
--- /dev/null
+++ b/test/mjsunit/compiler/regress-694088.js
@@ -0,0 +1,29 @@
+// Copyright 2017 the V8 project authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+(function () {
+  var buffer = new ArrayBuffer(8);
+  var i32 = new Int32Array(buffer);
+  var f64 = new Float64Array(buffer);
+
+  function foo() {
+    f64[0] = 1;
+    var x = f64[0];
+    return i32[0];
+  }
+  assertEquals(0, foo());

[JaideepBajwa, 2017/03/01 21:52:18]

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());

+})();
+
+(function () {
+  var buffer = new ArrayBuffer(8);
+  var i16 = new Int16Array(buffer);
+  var i32 = new Int32Array(buffer);
+
+  function foo() {
+    i32[0] = 0x10001;
+    var x = i32[0];
+    return i16[0];
+  }
+  assertEquals(1, foo());
+})();