Introduce runtime function %OptimizeFunctionOnNextCall to manually trigger optimization.

test/mjsunit/compiler/property-refs.js

Index: test/mjsunit/compiler/property-refs.js
diff --git a/test/mjsunit/compiler/property-refs.js b/test/mjsunit/compiler/property-refs.js
index 3f6f7937c36ed57493c68f99298b9f4c5f8bcd41..917b97d8c48f05ed2463225d349e0e38329378ab 100644
--- a/test/mjsunit/compiler/property-refs.js
+++ b/test/mjsunit/compiler/property-refs.js
@@ -25,6 +25,8 @@
 // (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
 // OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
+// Flags: --allow-natives-syntax
+
 function Load(o) {
   return o.outer.x | o.outer.inner.y;
 }
@@ -45,7 +47,11 @@ function LoadXY(x, y) {
   return Load(object);
 }
 
-for (var i = 0; i < 10000; i++) LoadXY(i, i);
+for (var i = 0; i < 5; i++) LoadXY(i, i);
+%OptimizeFunctionOnNextCall(StoreXY);

[Mads Ager (chromium), 2011/04/11 11:06:38]

Similarly here. If you do not optimize this here, does StoreXY get inlined in
LoadXY?

[Jakob Kummerow, 2011/04/11 12:55:51]

Yes, StoreXY does get inlined if only LoadXY is optimized explicitly. Removed
the two unnecessary lines.

+LoadXY(6, 6);
+%OptimizeFunctionOnNextCall(LoadXY);
+LoadXY(7, 7);
 assertEquals(42 | 87, LoadXY(42, 87));
 assertEquals(42 | 87, LoadXY(42, 87));
 assertEquals(42 | 99, LoadXY(42, "99"));