The -Xmaxjitcodesize flag was marked as obsolete on Solaris at least as far back as 2002 (JDK 1.4.0)! Yet at some point it was made an alias for -XX:ReservedCodeCacheSize and is processed prior to obsolete-option handling and so was not in fact obsolete.
It's time to look at this flag again and go through the removal process if it is not actually intended to be used.
It should also be noted that this flag is incorrectly documented e.g.
https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html
-Xmaxjitcodesize=size
Specifies the maximum code cache size (in bytes) for JIT-compiled code. Append the letter k or K to indicate kilobytes, m or M to indicate megabytes, g or G to indicate gigabytes. The default maximum code cache size is 240 MB; if you disable tiered compilation with the option -XX:-TieredCompilation, then the default size is 48 MB:
-Xmaxjitcodesize=240m
This option is equivalent to -XX:ReservedCodeCacheSize.
---
In fact this option does not take an equal sign and is used as:
-Xmaxjitcodesize240m
so at a minimum a doc task is needed to fix this.
It's time to look at this flag again and go through the removal process if it is not actually intended to be used.
It should also be noted that this flag is incorrectly documented e.g.
https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html
-Xmaxjitcodesize=size
Specifies the maximum code cache size (in bytes) for JIT-compiled code. Append the letter k or K to indicate kilobytes, m or M to indicate megabytes, g or G to indicate gigabytes. The default maximum code cache size is 240 MB; if you disable tiered compilation with the option -XX:-TieredCompilation, then the default size is 48 MB:
-Xmaxjitcodesize=240m
This option is equivalent to -XX:ReservedCodeCacheSize.
---
In fact this option does not take an equal sign and is used as:
-Xmaxjitcodesize240m
so at a minimum a doc task is needed to fix this.
- relates to
-
JDK-8213760 os::obsolete_option is obsolete and should be removed
- Resolved