JDK-8137160 : Use Compile::live_nodes instead of Compile::unique() in appropriate places -- followup
- Type: Enhancement
- Component: hotspot
- Sub-Component: compiler
- Affected Version: 9
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2015-09-25
- Updated: 2015-11-19
- Resolved: 2015-10-08
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.
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 b89Fixed  |
Related Reports
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
Description
To reduce the C2 compiler's memory usage, JDK-8011858 changed memory allocation for compiler-related data structures to use Compile::live_nodes() instead of Compile::unique_nodes(). While backporting JDK-8011858 to 8u72, we've discovered two code locations where live_nodes() and be used instead of unique_nodes(). This issue looks into whether allocation at these two code locations can be adjusted for 9 as well. Also, the current issue looks into other code locations where an adjustment is possible.