JDK-8204834 : Fix confusing "allocate" naming in OopStorage
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 11,12
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2018-06-12
  • Updated: 2021-04-20
  • Resolved: 2018-07-09
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 11 JDK 12
11.0.8-oracleFixed 12 b02Fixed
Related Reports
Relates :  
JDK-8204097 - Simplify OopStorage::AllocateList block entry access
Description
The review of JDK-8204097 showed that the "allocate list" nomenclature used internally in OopStorage is confusing.  It should have been "allocation list".  Make the following name changes throughout the implementation of OopStorage:

AllocateEntry => AllocationListEntry
AllocateList => AllocationList
_allocate_entry => _allocation_list_entry  
_allocate_list => _allocation_list
allocate_entry() => allocation_list_entry()  
allocate_list() => allocation_list()
  -- these functions are particularly confusing, since they don't
     allocate anything.
Comments
jdk11 backport request I would like to have the patch in openjdk11 as well (for better parity with 11.0.8_oracle). The patch applies cleanly.
12-05-2020