JDK-8133805 : Remove the bot_updates parameter from G1Allocator's allocation methods
- Type: Enhancement
- Component: hotspot
- Sub-Component: gc
- Affected Version: 9
- Priority: P5
- Status: Closed
- Resolution: Fixed
- Submitted: 2015-08-18
- Updated: 2018-02-16
- Resolved: 2017-12-20
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 10 | JDK 11 |
|---|---|
10Fixed  |
11 b01Fixed |
Related Reports
|
Duplicate :
|
|
|
Relates :
|
Description
The bot_updates parameter for the allocation methods is not necessary any more as the relevant G1AllocRegion instance for a particular allocation already has a _bot_updates member. Actually there are several asserts in the code that make sure that the bot_updates parameter passed down equals the _bot_updates member of G1AllocRegion. Some comments in the code indicates that passing the bot_updates parameter explicitly is an optimization that allows the compiler to compile out some branch. Look at whether this actually has any significant impact.