# HG changeset patch # User Thomas Wuerthinger # Date 1391605374 -3600 # Node ID 64b9375246e4107bc49fb299a314b9db3ef56166 # Parent c6b1802ae32b4479f9efff39c98c9322c9e00a12 Update README and AUTHORS. Move to HTML format. diff -r c6b1802ae32b -r 64b9375246e4 AUTHORS.html --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/AUTHORS.html Wed Feb 05 14:02:54 2014 +0100 @@ -0,0 +1,27 @@ +

Graal Authors

+ +The GraalVM is based on the source code of HotSpot. The following authors have contributed to the Graal-specific part of the source base: + + diff -r c6b1802ae32b -r 64b9375246e4 GRAAL_AUTHORS --- a/GRAAL_AUTHORS Wed Feb 05 12:16:56 2014 +0100 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,12 +0,0 @@ -Gilles Duboscq (gdub) -Peter Hofer -Christian Haeubl (chaeubl) -Christian Humer (chumer) -Roland Schatz -Doug Simon (dnsimon) -Lukas Stadler (lstadler) -Alexander Stipsits -Katrin Strassl -Christian Wimmer (cwimmer) -Andreas Woess (aw) -Thomas Wuerthinger (thomaswue) diff -r c6b1802ae32b -r 64b9375246e4 README --- a/README Wed Feb 05 12:16:56 2014 +0100 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,14 +0,0 @@ -README: - This file should be located at the top of the hotspot Mercurial repository. - - See http://openjdk.java.net/ for more information about the OpenJDK. - - See ../README-builds.html for complete details on build machine requirements. - -Simple Build Instructions: - - cd make && gnumake - - The files that will be imported into the jdk build will be in the "build" - directory. - diff -r c6b1802ae32b -r 64b9375246e4 README.html --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/README.html Wed Feb 05 14:02:54 2014 +0100 @@ -0,0 +1,81 @@ +

Building Graal

+

There is a Python script in mxtool/mx.py that simplifies working with the code +base. It requires Python 2.7. While you can run this script by using an absolute path, +it's more convenient to add graal/mxtool to your PATH environment variable so that the +'mx' helper script can be used. The following instructions in this file assume this +setup.

+ +

Building both the Java and C++ source code comprising the Graal VM +can be done with the following simple command.

+ +
+% mx build
+
+ +

There are a number of VM configurations supported by mx which can +be explicitly specified using the --vm option. However, you'll typically +want one of these VM configurations:

+ +
    +
  1. The 'server' configuration is a standard HotSpot VM that includes the + runtime support for Graal but uses the existing compilers for normal + compilation (e.g., when the interpreter threshold is hit for a method). + Compilation with Graal is only done by explicit requests to the + Graal API. This is how Truffle uses Graal.
    2. + +
  2. The 'graal' configuration is a VM where all compilation is performed + by Graal and no other compilers are built into the VM binary. This + VM will bootstrap Graal itself at startup unless the -XX:-BootstrapGraal + VM option is given.
    3. +
+ +

Unless you use the --vm option with the build command, you will be presented +with a dialogue to choose one of the above VM configurations for the build +as well as have the option to make it your default for subsequent commands +that need a VM specified.

+ +

To build the debug or fastdebug builds:

+ +
+% mx --vmbuild debug build
+% mx --vmbuild fastdebug build
+
+ +

Running Graal

+ +

To run the VM, use 'mx vm' in place of the standard 'java' command:

+ +
+% mx vm ...
+
+ +

To select the fastdebug or debug builds of the VM:

+ +
+% mx --vmbuild fastdebug vm ...
+% mx --vmbuild debug vm ...
+
+ +

Other VM Configurations

+ +

In addition to the VM configurations described above, there are +VM configurations that omit all VM support for Graal:

+ +
+% mx --vm server-nograal build
+% mx --vm server-nograal vm -version
+java version "1.7.0_25"
+Java(TM) SE Runtime Environment (build 1.7.0_25-b15)
+OpenJDK 64-Bit Server VM (build 25.0-b43-internal, mixed mode)
+
+ +
+% mx --vm client-nograal build
+% mx --vm client-nograal vm -version
+java version "1.7.0_25"
+Java(TM) SE Runtime Environment (build 1.7.0_25-b15)
+OpenJDK 64-Bit Cleint VM (build 25.0-b43-internal, mixed mode)
+
+ +

These configurations aim to match as closely as possible the +VM(s) included in the OpenJDK binaries one can download.

diff -r c6b1802ae32b -r 64b9375246e4 README_GRAAL.txt --- a/README_GRAAL.txt Wed Feb 05 12:16:56 2014 +0100 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,70 +0,0 @@ -Building Graal --------------- -There is a Python script in mxtool/mx.py that simplifies working with the code -base. It requires Python 2.7. While you can run this script by using an absolute path, -it's more convenient to add graal/mxtool to your PATH environment variable so that the -'mx' helper script can be used. The following instructions in this file assume this -setup. - -Building both the Java and C++ source code comprising the Graal VM -can be done with the following simple command. - -% mx build - -There are a number of VM configurations supported by mx which can -be explicitly specified using the --vm option. However, you'll typically -want one of these VM configurations: - -1. The 'server' configuration is a standard HotSpot VM that includes the - runtime support for Graal but uses the existing compilers for normal - compilation (e.g., when the interpreter threshold is hit for a method). - Compilation with Graal is only done by explicit requests to the - Graal API. This is how Truffle uses Graal. - -2. The 'graal' configuration is a VM where all compilation is performed - by Graal and no other compilers are built into the VM binary. This - VM will bootstrap Graal itself at startup unless the -XX:-BootstrapGraal - VM option is given. - -Unless you use the --vm option with the build command, you will be presented -with a dialogue to choose one of the above VM configurations for the build -as well as have the option to make it your default for subsequent commands -that need a VM specified. - -To build the debug or fastdebug builds: - -% mx --vmbuild debug build -% mx --vmbuild fastdebug build - -Running Graal -------------- - -To run the VM, use 'mx vm' in place of the standard 'java' command: - -% mx vm ... - -To select the fastdebug or debug builds of the VM: - -% mx --vmbuild fastdebug vm ... -% mx --vmbuild debug vm ... - -Other VM Configurations ------------------------ - -In addition to the VM configurations described above, there are -VM configurations that omit all VM support for Graal: - -% mx --vm server-nograal build -% mx --vm server-nograal vm -version -java version "1.7.0_25" -Java(TM) SE Runtime Environment (build 1.7.0_25-b15) -OpenJDK 64-Bit Server VM (build 25.0-b43-internal, mixed mode) - -% mx --vm client-nograal build -% mx --vm client-nograal vm -version -java version "1.7.0_25" -Java(TM) SE Runtime Environment (build 1.7.0_25-b15) -OpenJDK 64-Bit Cleint VM (build 25.0-b43-internal, mixed mode) - -These configurations aim to match as closely as possible the -VM(s) included in the OpenJDK binaries one can download. \ No newline at end of file