[Graal] AOTed JVMCI causes exception and doesnt run

XMLWordPrintable

      While running some JMH where graal, java.base, and jvmci are AOTed, an exception happens:

      # Run progress: 0.00% complete, ETA 00:08:20
      # Fork: 1 of 5
      Uncaught exception at /home/eric/tmp/jenkins/workspace/Buijladv-aj.dlka-nngi.gNhotCllya-swsiDtehf-FAoOuTn-dDEerlrl/ojrd:k /oorpen/src/hotsgpo/tg/rasahlavrme//cjovmmpciil/ejrv/mhcoitCsopmopti/lHeort.Scppopt:G1r4a1a
      lJVMCIServiceLocator$Shared
      at jdk.internal.vm.compiler@12-internal/org.graalvm.compiler.hotspot.HotSpotGraalJVMCIServiceLocator.getProvider(HotSpotGraalJVMCIServiceLocator.java:67)
      at jdk.internal.vm.ci/jdk.vm.ci.services.JVMCIServiceLocator.getProviders(JVMCIServiceLocator.java:88)
      at jdk.internal.vm.ci/jdk.vm.ci.hotspot.HotSpotJVMCICompilerConfig.getCompilerFactory(HotSpotJVMCICompilerConfig.java:91)
      at jdk.internal.vm.ci/jdk.vm.ci.hotspot.HotSpotJVMCIRuntime.<init>(HotSpotJVMCIRuntime.java:297)
      at jdk.internal.vm.ci/jdk.vm.ci.hotspot.HotSpotJVMCIRuntime$DelayedInit.<clinit>(HotSpotJVMCIRuntime.java:80)
      at jdk.internal.vm.ci/jdk.vm.ci.hotspot.HotSpotJVMCIRuntime.runtime(HotSpotJVMCIRuntime.java:96)
      at jdk.internal.vm.ci/jdk.vm.ci.runtime.JVMCI.initializeRuntime(Native Method)
      at jdk.internal.vm.ci/jdk.vm.ci.runtime.JVMCI.<clinit>(JVMCI.java:58)
      <forked VM failed with exit code 255>
      <stdout last='20 lines'>
      Uncaught exception at /home/eric/tmp/jenkins/workspace/Build-jdk-nightly-with-AOT-Dell/jdk/open/src/hotspot/share/jvmci/jvmciCompiler.cpp:141
      </stdout>
      <stderr last='20 lines'>
      java.lang.NoClassDefFoundError: org/graalvm/compiler/hotspot/HotSpotGraalJVMCIServiceLocator$Shared
      at jdk.internal.vm.compiler@12-internal/org.graalvm.compiler.hotspot.HotSpotGraalJVMCIServiceLocator.getProvider(HotSpotGraalJVMCIServiceLocator.java:67)
      at jdk.internal.vm.ci/jdk.vm.ci.services.JVMCIServiceLocator.getProviders(JVMCIServiceLocator.java:88)
      at jdk.internal.vm.ci/jdk.vm.ci.hotspot.HotSpotJVMCICompilerConfig.getCompilerFactory(HotSpotJVMCICompilerConfig.java:91)
      at jdk.internal.vm.ci/jdk.vm.ci.hotspot.HotSpotJVMCIRuntime.<init>(HotSpotJVMCIRuntime.java:297)
      at jdk.internal.vm.ci/jdk.vm.ci.hotspot.HotSpotJVMCIRuntime$DelayedInit.<clinit>(HotSpotJVMCIRuntime.java:80)
      at jdk.internal.vm.ci/jdk.vm.ci.hotspot.HotSpotJVMCIRuntime.runtime(HotSpotJVMCIRuntime.java:96)
      at jdk.internal.vm.ci/jdk.vm.ci.runtime.JVMCI.initializeRuntime(Native Method)
      at jdk.internal.vm.ci/jdk.vm.ci.runtime.JVMCI.<clinit>(JVMCI.java:58)
      </stderr>

      # Run complete. Total time: 00:00:00

      REMEMBER: The numbers below are just data. To gain reusable insights, you need to follow up on
      why the numbers are the way they are. Use profilers (see -prof, -lprof), design factorial
      experiments, perform baseline and negative tests that provide experimental control, make sure
      the benchmarking environment is safe on JVM/OS/HW level, ask for reviews from the domain experts.
      Do not assume the numbers tell you what you want them to tell.

      Benchmark Mode Cnt Score Error Units

            Assignee:
            Igor Veresov
            Reporter:
            Eric Caspole
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: