JDK-8146547 : String copy intrinsics should zero array in case of tightly coupled allocation
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 9,10
  • Priority: P5
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2016-01-06
  • Updated: 2020-05-07
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.
Related Reports
Duplicate :  
Relates :  
LibraryCallKit::inline_string_copy() and LibraryCallKit::inline_string_getCharsU() use LibraryCallKit::tightly_coupled_allocation() to skip zeroing the array elements of a tightly coupled array allocation. However, the intrinsics do not take care of zeroing remaining array elements not affected by the intrinsic operation.
Currently, this is not a problem because all (String API internal) usages of the intrinsics that have a tightly coupled allocation make sure that the entire array is initialized. However, we should fix this to avoid potential bugs.
ILW = potential risk of uninitialized wth 0 arrays in String internals; no cases with failures; manual zeroing of arrays = MLL = P5