JDK-8305351 : C2 setScopedValueCache intrinsic doesn't use access API
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 21
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2023-03-31
  • Updated: 2023-04-24
  • Resolved: 2023-04-17
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 21
21 b19Fixed
Related Reports
Relates :  
JDK-8284161 - Implementation of Virtual Threads (Preview)
Description
The setScopedValueCache intrinsic for C2 doesn't use the access API. Instead, we store into an OopHandle with a raw store. That doesn't play well with all GCs, for example Shenandoah and generational ZGC. We should use the access API
Comments
Changeset: 02347d0c Author: Erik Österlund <eosterlund@openjdk.org> Date: 2023-04-17 12:14:57 +0000 URL: https://git.openjdk.org/jdk/commit/02347d0cec77212d38aad8d06b6ac0c316be00d7
17-04-2023
A pull request was submitted for review. URL: https://git.openjdk.org/jdk/pull/13324 Date: 2023-04-04 12:40:14 +0000
04-04-2023
ILW = Not using access API could lead to problems for some GCs, not observed yet?, use GC other than Shenandoah or generational ZGC = MLH = P4
03-04-2023