Backports
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8193523 | 10 | Leo Korinth | P5 | Resolved | Fixed | b37 |
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.
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.
Attachments
Issue Links
- backported by
-
JDK-8193523 Remove the bot_updates parameter from G1Allocator's allocation methods
-
- Resolved
-
- duplicates
-
-
- Resolved
-
- relates to
-
JDK-8030849 Investigate high fragmentation/waste in some situations during allocation during GC in G1
-
- Open
-