Fix elements-kind test to disable optimization of important functions under test; add simpler versi…

test/mjsunit/elements-kind.js

Index: test/mjsunit/elements-kind.js
diff --git a/test/mjsunit/elements-kind.js b/test/mjsunit/elements-kind.js
index 0e8e209ef7e9ffdd16ced1017b6945a850fe5431..247aa8974758cad96d3968be4f3a92def0acae06 100644
--- a/test/mjsunit/elements-kind.js
+++ b/test/mjsunit/elements-kind.js
@@ -171,18 +171,21 @@ monomorphic(smi_only);
 
 if (support_smi_only_arrays) {
   function construct_smis() {
+    try {} catch (e) {} // TODO(titzer): DisableOptimization
     var a = [0, 0, 0];
     a[0] = 0;  // Send the COW array map to the steak house.
     assertKind(elements_kind.fast_smi_only, a);
     return a;
   }
   function construct_doubles() {
+    try {} catch (e) {} // TODO(titzer): DisableOptimization
     var a = construct_smis();
     a[0] = 1.5;
     assertKind(elements_kind.fast_double, a);
     return a;
   }
   function construct_objects() {
+    try {} catch (e) {} // TODO(titzer): DisableOptimization
     var a = construct_smis();
     a[0] = "one";
     assertKind(elements_kind.fast, a);
@@ -191,6 +194,7 @@ if (support_smi_only_arrays) {
 
   // Test crankshafted transition SMI->DOUBLE.
   function convert_to_double(array) {
+    try {} catch (e) {} // TODO(titzer): DisableOptimization
     array[1] = 2.5;
     assertKind(elements_kind.fast_double, array);
     assertEquals(2.5, array[1]);
@@ -202,6 +206,7 @@ if (support_smi_only_arrays) {
   convert_to_double(smis);
   // Test crankshafted transitions SMI->FAST and DOUBLE->FAST.
   function convert_to_fast(array) {
+    try {} catch (e) {} // TODO(titzer): DisableOptimization
     array[1] = "two";
     assertKind(elements_kind.fast, array);
     assertEquals("two", array[1]);
@@ -218,6 +223,7 @@ if (support_smi_only_arrays) {
   // Test transition chain SMI->DOUBLE->FAST (crankshafted function will
   // transition to FAST directly).
   function convert_mixed(array, value, kind) {
+    try {} catch (e) {} // TODO(titzer): DisableOptimization

[mvstanton, 2013/06/26 13:21:43]

What is the timeframe to bring these back to allow optimization, I ask because
it looks like the intent of this test is to verify that things work as expected
in the full codegen and crankshaft cases. If we don't test the crankshaft case,
regressions could slip in. Is there another way to achieve what you are looking
for, like making a copy of this test and specifying different flags?

[titzer, 2013/06/26 17:53:59]

As it turns out, what this test does is check the elements kind transitions that
happen in fullcode; i.e. it will not work if the methods in question are
compiled with crankshaft, which transitions the elements kinds differently. As
it turns out, these methods were never being compiled with Crankshaft, and when
I added a mode to do aggressive OSR (including the toplevel code here, which
then inlines these methods), then one of this test's asserts fails.

I'm not a big fan of tests for optimization states, in particular this one, but
at least this way, the tests' requirements are explicit. Before, we were just
lucky.

     array[1] = value;
     assertKind(kind, array);
     assertEquals(value, array[1]);