JDK-8312579 : [JVMCI] JVMCI support for virtual Vector API objects
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 17,21,22
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2023-07-24
  • Updated: 2024-01-22
  • Resolved: 2023-07-27
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 22
22 b09Fixed
Related Reports
Relates :  
JDK-8223347 - Integration of Vector API (Incubator)
Relates :  
JDK-8313530 - VM build without C2 fails after JDK-8312579
Relates :  
JDK-8324341 - Remove useless COMPILER2_OR_JVMCI checks
Description
Optimized Vector API values are represented as raw values in SIMD registers. When deoptimizing with such a value in the state, a Java heap object must be recreated. HotSpot has a special "Location::vector" location type to mark Vector API values, and it knows how to materialize such values.

Extend the JVMCI code installer to mark the appropriate values as vectors so that JVMCI-compiled code can also deoptimize with Vector API values in SIMD registers.
Comments
Changeset: 271417a0 Author: Gergö Barany <gbarany@openjdk.org> Committer: Doug Simon <dnsimon@openjdk.org> Date: 2023-07-27 10:48:18 +0000 URL: https://git.openjdk.org/jdk/commit/271417a0e10245504e41c98c65941d5fe21f33ac
27-07-2023
A pull request was submitted for review. URL: https://git.openjdk.org/jdk/pull/15003 Date: 2023-07-24 18:58:02 +0000
24-07-2023
ILW = Missing support for Vector API, Vector API (incubator) with JVMCI, no workaround = MMH = P3
24-07-2023