RFR(M) 8182701: Modify JVMCI to allow Graal Compiler to expose platform MBean
jaroslav.tulach at oracle.com
Thu Aug 3 15:06:01 UTC 2017
On čtvrtek 27. července 2017 15:01:17 CEST Alan Bateman wrote:
> On 27/07/2017 10:07, Jaroslav Tulach wrote:
> > Yes, it seems like a desirable goal to let Graal compiler work with just
> > java.base. Is there a description how to build JDK9/10 with just java.base
> > that I could follow and test against?
> You can use jlink to create a run-time image that only contains
> java.base (jlink --module-path $JAVA_HOME/jmods --add-modules java.base
> --output smalljre).
Status update: I've just tried to run Graal compiler against JDK9 with only
java.base and jdk.internal.vm.ci modules, and there are some problems. I need
to resolve them first before I provide updated version of my patch.
Thanks for your support so far.
> >> If it exposes a MBean, the dependency would be needed.
> > Isn't there a way to require an optional dependency? That would be
> > sufficient - as the classes in question are only loaded once
> > java.management searches for them. E.g. only when java.management is
> > installed.
> There is `requires static` but it would be a lot cleaner if the
> management support could be refactored into its own service provider
> module, meaning JVMCIMXBeans would be in its own module.
More information about the hotspot-compiler-dev