RFR: 8312579: [JVMCI] JVMCI support for virtual Vector API objects [v2]
Doug Simon
dnsimon at openjdk.org
Wed Jul 26 07:56:42 UTC 2023
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
Yes, I believe so. Gergo, you should scan all other code guarded by `EnableVectorSupport` to see if there's a similar problem.
-------------
PR Comment: https://git.openjdk.org/jdk/pull/15003#issuecomment-1651170939
More information about the hotspot-compiler-dev
mailing list