P3
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.
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.
- relates to
-
JDK-8223347 Integration of Vector API (Incubator)
-
- Resolved
-
-
JDK-8324341 Remove redundant preprocessor #if's checks
-
- Resolved
-
-
JDK-8313530 VM build without C2 fails after JDK-8312579
-
- Resolved
-
