Mercurial > hg > graal-jvmci-8
changeset 21154:271eee87201c
Update readme and changelog
author | Gilles Duboscq <gilles.m.duboscq@oracle.com> |
---|---|
date | Wed, 29 Apr 2015 15:27:00 +0200 |
parents | 1621af5cb444 |
children | 754f2b20d8bc |
files | CHANGELOG.md README.md |
diffstat | 2 files changed, 16 insertions(+), 11 deletions(-) [+] |
line wrap: on
line diff
--- a/CHANGELOG.md Wed Apr 29 14:41:03 2015 +0200 +++ b/CHANGELOG.md Wed Apr 29 15:27:00 2015 +0200 @@ -5,14 +5,20 @@ ## `tip` ### Graal +* By default the Graal code is now only compiled by C1 which should improve application start-up. * Merged with jdk8u40-b25. +* The Graal class loader now loads all lib/graal/graal*.jar jars. +* Fast Graal services (see com.oracle.graal.api.runtime.Service) are now looked up using service files in lib/graal/services * Add utilities ModifiersProvider#isConcrete, ResolvedJavaMethod#hasBytecodes, ResolvedJavaMethod#hasReceiver to Graal API. * Add `GraalDirectives` API, containing methods to influence compiler behavior for unittests and microbenchmarks. * Introduce `LIRSuites`, an extensible configuration for the low-level compiler pipeline. -* The Graal class loader now loads all lib/graal/graal*.jar jars. * ... ### Truffle +* New, faster partial evaluation (no more TruffleCache). +* If a method is annotated with @ExplodeLoop and contains a loop that can not be exploded, partial evaluation will fail. +* Truffle background compilation is now multi-threaded. +* Experimental merge=true flag for @ExplodeLoop allows building bytecode-based interpreters (see BytecodeInterpreterPartialEvaluationTest). * Added Node#deepCopy as primary method to copy ASTs. * Disable inlining across Truffle boundary by default. New option TruffleInlineAcrossTruffleBoundary default false. * Node.replace(Node) now guards against non-assignable replacement, and Node.isReplacementSafe(Node) checks in advance.
--- a/README.md Wed Apr 29 14:41:03 2015 +0200 +++ b/README.md Wed Apr 29 15:27:00 2015 +0200 @@ -24,10 +24,8 @@ Graal API. This is how Truffle uses Graal. 2. The 'graal' configuration is a VM where normal compilations are performed - by Graal. This VM will bootstrap Graal itself at startup unless the - -XX:-BootstrapGraal. Note that if tiered compilation is enabled, Graal - will be used at the last tier while C1 will be used for the first compiled - tiers. + by Graal. By default tiered compilation is enabled and Graal will be used at + the last tier while C1 will be used for the first compiled tiers. 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 @@ -64,17 +62,18 @@ ``` % 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) +java version "1.8.0_40" +Java(TM) SE Runtime Environment (build 1.8.0_40-b25) +OpenJDK 64-Bit Server VM (build 25.40-b25-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 Client VM (build 25.0-b43-internal, mixed mode) +java version "1.8.0_40" +Java(TM) SE Runtime Environment (build 1.8.0_40-b25) +OpenJDK 64-Bit Client VM (build 25.40-b25-internal, mixed mode) ``` These configurations aim to match as closely as possible the