view GRAAL_README @ 3193:52087773be5b

IdealGraphVisualizer: Make scheduling more robust by ignoring graphs without any nodes and by using the node with the lowest id as root when there is no node labeled "Root" and no node without predecessors
author Peter Hofer <peter.hofer@jku.at>
date Fri, 08 Jul 2011 14:26:12 +0200
parents ea778c37bdae
children d8c27956ec6e
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:
-client KNOWN

Before running the Graal VM, the following environment variables are needed:
- MAXINE: Pointing to a Maxine VM repository with compiled Java files.
- GRAAL: Pointing to a Graal 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
${GRAAL}/graal/com.oracle.max.graal.compiler/bin
${GRAAL}/graal/com.oracle.max.graal.runtime/bin
${GRAAL}/graal/com.oracle.max.graal.graphviz/bin

For starting the Graal VM, the two flags "-client -graal" have 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.