RFR: 8312579: [JVMCI] JVMCI support for virtual Vector API objects [v2]

[Xiaohong Gong]

On Tue, 25 Jul 2023 10:20:54 GMT, Gergö Barany <gbarany at openjdk.org> wrote:

>> 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.
>
> Gergö Barany has updated the pull request incrementally with two additional commits since the last revision:
> 
>  - Improve parameter naming
>  - Rewrite nested ternary expressions

Does it need to update `#ifdef COMPILER2` to `#if COMPILER2_OR_JVMCI` in https://github.com/openjdk/jdk/blob/master/src/hotspot/share/runtime/deoptimization.cpp#L1238 which is the gateway of re-materializing a Vector API object from vector register/stack?

-------------

PR Comment: https://git.openjdk.org/jdk/pull/15003#issuecomment-1650868591