From: jjenista Date: Mon, 1 Nov 2010 19:50:13 +0000 (+0000) Subject: the mismatch of sequential and ooo goes away if you remove the semantically-benign... X-Git-Url: http://plrg.eecs.uci.edu/git/?a=commitdiff_plain;h=e1dbf520a0dd73935e6c44a9715b16f015b43ff5;p=IRC.git the mismatch of sequential and ooo goes away if you remove the semantically-benign explicit parent of this micro benchmark. It means our system still has bugs, but this pattern doesn't appear in the normal benchmarks so the problem is best deferred until it impacts results --- diff --git a/Robust/src/Benchmarks/oooJava/micro2.5/test.java b/Robust/src/Benchmarks/oooJava/micro2.5/test.java index 67b2acac..6804076b 100644 --- a/Robust/src/Benchmarks/oooJava/micro2.5/test.java +++ b/Robust/src/Benchmarks/oooJava/micro2.5/test.java @@ -2,7 +2,7 @@ public class test { public static void main( String argv[] ) { - long count = 500000; + long count = 50000; if( argv.length > 0 ) { count = count * Integer.parseInt( argv[0] ); @@ -12,8 +12,9 @@ public class test { long e1; long e2; - - rblock parent { + // THIS PARENT SHOULD NOT AFFECT ANYTHING + // BUT IT BREAKS THE OOO BINARY!! + //rblock parent { long y = 0; @@ -33,12 +34,12 @@ public class test { } e1 = System.currentTimeMillis(); - long z = 1; - } + //long z = 1; + //} // just read vars so compile doesn't throw them out // and force parent of parent to depend on z, for // timing - System.out.println( "ignore: "+z+", "+y ); + System.out.println( "ignore: "+y ); e2 = System.currentTimeMillis();