view GRAAL_README @ 4612:d8ff6f2bcabd

Use parameters in graph group names for the visualizer so that successive compilation of methods with same name but different signature don't get fused Made CFGPrinterObserver a bit more robust to failed schedule When an exception occurs while intercepting exception, this new exception should be seen
author Gilles Duboscq <duboscq@ssw.jku.at>
date Wed, 15 Feb 2012 20:05:06 +0100
parents d8c27956ec6e
children
line wrap: on
line source

For creating a Graal VM JDK, the file jre\lib\jvm.cfg has to be modified such that it includes the line:
-graal KNOWN

Before running the Graal VM, the following environment variables is needed:
- MAXINE: Pointing to a Maxine VM repository with compiled Java files.

In particular, the VM will look for the compiled Java files in the following directories:
${MAXINE}/com.oracle.max.cri/bin
${MAXINE}/com.oracle.max.base/bin
${MAXINE}/com.oracle.max.asmdis/bin
${MAXINE}/com.oracle.max.asm/bin
${MAXINE}/com.oracle.max.graal.graph/bin
${MAXINE}/com.oracle.max.graal.compiler/bin
${MAXINE}/com.oracle.max.graal.nodes/bin
${MAXINE}/com.oracle.max.graal.extensions/bin
${MAXINE}/com.oracle.max.graal.runtime/bin
${MAXINE}/com.oracle.max.graal.graphviz/bin

For starting the Graal VM, the flag "-graal" has to be specified. Additional flags that might be useful:
-G:Plot Sends the graphs of compiled methods via network stream to the IdealGraphVisualizer (NetBeans project at ${GRAAL}/src/share/tools/IdealGraphVisualizer that can be built and run with NetBeans 7.0, use "Graal Coloring" and "Graal Edge Coloring" filters)
-G:Time Prints timings for the different compilation phases
-G:Meter Prints metrics for the different compilation phases

The usual HotSpot flags -Xcomp -XX:CompileOnly= -XX:CompileCommand= or -XX:+PrintCompilation can be used to control the compiled methods.