Problem building graal on x86

Andrew Dinn adinn at
Fri Jan 13 13:50:13 UTC 2017

On 12/01/17 18:51, Andrew Haley wrote:
> On 12/01/17 18:09, Doug Simon wrote:
>> The latest jigsaw refresh has caused quite some issues for Graal
>> compatibility. So unless you have lots of spare time, I’d recommend
>> sticking with b143 and wait until I complete the work mentioned
>> above.
> b143 is from before the AArch64 JVMCI changes went in, so no can do
> that.
> I can't find any version of OpenJDK which works with the current Graal
> and works with AArch64.  I can't think that I'm going to have any
> choice but to try to debug the Jigsaw-related bugs.  I've tried b148,
> which Andrew Dinn says works for him on x86, but no luck.

I appear to have  managed to get past the Jigsaw issues by running with
b148 and adding some jigsaw config option to the command line:

$ mx --java-home ~/jdk9-b148/j2sdk-image vm -XX:+UseJVMCICompiler
-XX:+EnableJVMCI --add-exports --add-opens
java.base/jdk.internal.misc=org.graalvm.compiler.graal_core -cp
../../jdk9-dev HelloV

This gets past the problems with package access by making package public accessible for linking to graal_core code
(that's the add-exports) and by making package jdk.internal.misc both
public accessible for linking and also non-public accessible for
reflection (that's the add-opens).

With that I hit the following problem:

# A fatal error has been detected by the Java Runtime Environment:
#  Internal Error (jvmciCodeInstaller_aarch64.cpp:65), pid=26777, tid=26805
#  Error: Unimplemented()

Of course proceeding beyond this may need a few more -add-exports or
--add-opens but this may be all that is needed for now.


Andrew Dinn
Senior Principal Software Engineer
Red Hat UK Ltd
Registered in England and Wales under Company Registration No. 03798903
Directors: Michael Cunningham, Michael ("Mike") O'Neill, Eric Shander

More information about the graal-dev mailing list