The effort of maintaining JVMCI across different JDK versions (including a potential backport to JDK7) is reduced by making JVMCI as small as possible. The support for command line options in JVMCI (based around the @Option annotation) is a good candidate for removal:
1. It’s almost entirely implemented on top of system properties and so can be made to work without VM support.
2. JVMCI itself only currently uses 3 options which can be replaced with usage of sun.misc.VM.getSavedProperty(). The latter ensures application code can’t override JVMCI properties set on the command line.
This issue removes the JVMCI command line option support.
1. It’s almost entirely implemented on top of system properties and so can be made to work without VM support.
2. JVMCI itself only currently uses 3 options which can be replaced with usage of sun.misc.VM.getSavedProperty(). The latter ensures application code can’t override JVMCI properties set on the command line.
This issue removes the JVMCI command line option support.
- relates to
-
JDK-8146820 JVMCI options should not use System.getProperty directly
-
- Resolved
-