[tests] Make assertOptimized()/assertUnoptimized() great again.

test/mjsunit/regress/regress-v8-5697.js

Index: test/mjsunit/regress/regress-v8-5697.js
diff --git a/test/mjsunit/regress/regress-v8-5697.js b/test/mjsunit/regress/regress-v8-5697.js
index 5a88614b1355466e36839a3b7a72ee94b18d3897..66f15f2e09883286ab03d49149ce6e377f9be533 100644
--- a/test/mjsunit/regress/regress-v8-5697.js
+++ b/test/mjsunit/regress/regress-v8-5697.js
@@ -9,6 +9,7 @@ function load(o) { return o.x; }
 for (var x = 0; x < 1000; ++x) {
   load({x});
   load({x});
+  % OptimizeFunctionOnNextCall(load);

[Igor Sheludko, 2017/01/25 11:38:42]

Optimization of load() did not kick in with --ignition-staging.

[Michael Starzinger, 2017/01/26 12:24:52]

Is the loop still needed on this case?

[Igor Sheludko, 2017/01/26 14:12:30]

Yes. The test checks that we don't have a deopt loop here.

   try { load(); } catch (e) { }
 }
 
@@ -20,6 +21,7 @@ function store(o) { o.x = -1; }
 for (var x = 0; x < 1000; ++x) {
   store({x});
   store({x});
+  % OptimizeFunctionOnNextCall(store);

[Michael Starzinger, 2017/01/26 12:24:52]

Likewise.

   try { store(); } catch (e) { }
 }