1.1 --- a/make/project.properties Thu Oct 09 11:56:42 2014 +0200
1.2 +++ b/make/project.properties Thu Oct 09 10:19:24 2014 +0200
1.3 @@ -286,7 +286,8 @@
1.4 # turn on assertions for tests
1.5 run.test.jvmargs.main=${run.test.jvmargs.common} -ea
1.6
1.7 -# extra jvmargs that might be useful for debugging
1.8 +# Extra jvmargs that might be useful for debugging
1.9 +# and performance improvements/monitoring
1.10 #
1.11 # -XX:+UnlockDiagnosticVMOptions
1.12 #
1.13 @@ -304,9 +305,25 @@
1.14 #
1.15 # print all compiled nmethods with oopmaps and lots of other info
1.16 # -XX:+PrintNMethods
1.17 +#
1.18 +# activate the generic "UseNewCode" flag to test whatever functionality
1.19 +# lies behind it. This is the preferred way to test a, yet flagless,
1.20 +# feature in HotSpot - for example, the uncommon trap placement fix
1.21 +# was hidden behind this flag before it became the default
1.22 +#
1.23 +# -XX:+UnlockDiagnosticVMOptions -XX:+UseNewCode
1.24 +#
1.25 +# Crank up the type profile level to 222, which has some warmup
1.26 +# penalties, but produces much better code for JavaScript, where better
1.27 +# and more intrusive type profiling is required to get rid of
1.28 +# a large amount of unnecessary guard code, that could not otherwise
1.29 +# be eliminated
1.30 +#
1.31 +# -XX:TypeProfileLevel=222
1.32 +#
1.33
1.34 # Use best known performance options for octane
1.35 -run.test.jvmargs.octane.main=${run.test.jvmargs.common} -XX:+UnlockDiagnosticVMOptions -XX:+UseNewCode -XX:TypeProfileLevel=222
1.36 +run.test.jvmargs.octane.main=${run.test.jvmargs.common} -XX:TypeProfileLevel=222
1.37
1.38 # Security manager args - make sure that we run with the nashorn.policy that the build creates
1.39 run.test.jvmsecurityargs=-Xverify:all -Djava.security.manager -Djava.security.policy=${build.dir}/nashorn.policy
