Running jaotc with an external Graal
doug.simon at oracle.com
Tue Feb 14 13:34:47 UTC 2017
I don’t know how one patches a module in the middle of the module graph. That is, we use --patch-module and --upgrade-module-path to override the jdk.vm.compiler module in the JDK. I don’t know what that means for modules such as jdk.aot that depend on jdk.vm.compiler. Maybe someone from the AOT or jigsaw team can help.
> On 14 Feb 2017, at 12:26, Andrew Haley <aph at redhat.com> wrote:
> Is this possible? Seems that no matter what I do, aotc always prefers to
> use the internal version of org.graalvm.compiler which is in HotSpot.
> I don't quite get why this is: I can run an external Graal using JVMCI
> with no problems. I saw "8145337: [JVMCI] JVMCI initialization with
> SecurityManager installed fails:" which might be related, but perhaps
> it's not.
> So, why is it possible to use an external Graal with JVMCI, but
> apparently not with jaotc? And is there anything I can do to make
More information about the hotspot-compiler-dev