Fix for failing asserts in HBoundsCheck code generation on x64: use proper cmp operation width inst…

test/mjsunit/regress/regress-crbug-349465-1.js

Index: test/mjsunit/regress/regress-crbug-349465-1.js
diff --git a/test/mjsunit/regress/regress-crbug-349465-1.js b/test/mjsunit/regress/regress-crbug-349465-1.js
new file mode 100644
index 0000000000000000000000000000000000000000..2876c6cbe8d51c95a44cae518b7000d5c02cd787
--- /dev/null
+++ b/test/mjsunit/regress/regress-crbug-349465-1.js
@@ -0,0 +1,17 @@
+// Copyright 2014 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.
+
+// Flags: --allow-natives-syntax --debug-code
+
+__v_1 = new Int32Array(1024);

[Toon Verwaest, 2014/03/06 15:39:19]

Could you please sanitize these tests a bit? Try to reduce as much as possible,
and remove all the __ stuff. That'll just make it easier to understand the test
in the future.

[Igor Sheludko, 2014/03/06 17:21:20]

Done.

+function __f_2(__v_1, base, condition) {
+  __v_1[base + 1] = 1;
+  __v_1[base + 4] = 2;
+  __v_1[base + 0] = base + -1;
+}
+__f_2(__v_1, 1, true);
+__f_2(__v_1, -9, true);
+__v_2 = new Int32Array(128);
+%OptimizeFunctionOnNextCall(__f_2);
+__f_2(__v_2, -2, true);