JDK-8322476 : Remove GrowableArray C-Heap version, replace usages with GrowableArrayCHeap
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: runtime
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2023-12-19
  • Updated: 2024-07-23
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.
Other
tbdUnresolved
Related Reports
Relates :  
JDK-8319115 - GrowableArray: Do not initialize up to capacity
Description
We should more clearly separate the C-Heap version from the arena /  resource area allocation.

Advantages:
- If they are separate subclasses, then we have to do less verification when assigning, copying, allocating etc: fewer mistakes can happen.
- We can establish a clear separation between: take care of allocation/deallocation yourself (C-Heap) vs. abandon memory and the elements still in the array (arena / resource area).
- We should not have multiple implementations of the same thing (C-Heap backed array).
Comments
A pull request was submitted for review. URL: https://git.openjdk.org/jdk/pull/17160 Date: 2023-12-19 16:59:05 +0000
20-12-2023