Hi, I wanted to try to build a JVM on Linux x86_64 with JVMCI disabled (just to
check how the JVM behaves in a test).
The configure help output shows a long list how to enable those features
--enable-jvm-feature-cds
enable jvm feature 'cds' (enable class data sharing
(CDS))
--enable-jvm-feature-compiler1
enable jvm feature 'compiler1' (enable hotspot
compiler C1)
--enable-jvm-feature-compiler2
enable jvm feature 'compiler2' (enable hotspot
compiler C2)
--enable-jvm-feature-dtrace
enable jvm feature 'dtrace' (enable dtrace support)
--enable-jvm-feature-epsilongc
enable jvm feature 'epsilongc' (include the epsilon
(no-op) garbage collector)
--enable-jvm-feature-g1gc
enable jvm feature 'g1gc' (include the G1 garbage
collector)
--enable-jvm-feature-jfr
enable jvm feature 'jfr' (enable JDK Flight Recorder
(JFR))
--enable-jvm-feature-jni-check
enable jvm feature 'jni-check' (enable -Xcheck:jni
support)
--enable-jvm-feature-jvmci
enable jvm feature 'jvmci' (enable JVM Compiler
Interface (JVMCI))
--enable-jvm-feature-jvmti
enable jvm feature 'jvmti' (enable Java Virtual
Machine Tool Interface (JVM TI))
….
For disabling it seems the syntax --enable-jvm-feature-jvmci=no seems to work
.
Looking into make/autoconf/jvm-features.m4 this seems to be true for all JVM
features .
Should we add this to the help output ?
Would be useful to have some sentence like --enable-jvm-feature-<name>=no
can be used to disable a JVM feature .
Should we add this to the configure help ?
Thanks, Matthias
