JDK-8061436 : Processing of options related to segmented code cache should be enhanced
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 9
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2014-10-19
  • Updated: 2015-12-10
  • Resolved: 2015-11-16
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 9
9 b96Fixed
Related Reports
Duplicate :  
JDK-8059611 - Improve logic of 'Arguments::set_tiered_flags'
Description
With JEP 197 (JDK-8043304) three new option were added: NonNMethodCodeHeapSize,  NonProfiledCodeHeapSize and ProfiledCodeHeapSize. Sum of these options should be equal to ReservedCodeCacheSize, otherwise VM initialization will fail.

Unfortunately, current implementation requires manual change of ReservedCodeCacheSize's value if one of *CodeHeapSize options was explicitly changed.

So if user saw a warning saying that code heap was exhausted and some of *CodeHeapSize option's value should be increased, then she'll try to do that without changing the ReservedCodeCacheSize's value and most probably VM initialization will fail.

I'm suggesting to:
- derive ReservedCodeCacheSize value from *CodeHeapSize options' values when ReservedCodeCacheSize was not explicitly passed to JVM;
- automatically setup values of *CodeHeapSize options when one or two of them were explicitly passed as well as ReservedCodeCacheSize.