-
Notifications
You must be signed in to change notification settings - Fork 43
8253211: Make sure jvm does not crash with Arm SVE and Vector API #7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Add those vector api specific OPs to unsupported list for SVE.
👋 Welcome back njian! A progress list of the required criteria for merging this PR into |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good.
@nsjian This change now passes all automated pre-integration checks. In addition to the automated checks, the change must also fulfill all project specific requirements After integration, the commit message will be:
There are currently no new commits on the ➡️ To integrate this PR with the above commit message to the |
/integrate |
=== Currently we have not implemented all Arm SVE code generation for Vector API specific nodes. To make sure hotspot does not crash with bad AD file (as NEON has implemented them), we simply add those OPs to unsupported op list. This is the port and minor cleanup of JDK-8253211 in repo-panama: openjdk/panama-vector#7 with Op_VectorUnbox (not for codegen) and Op_VectorMaskWrapper (unused code?) removed from the unsupported op list and Op_VectorLoadConst added. Test: tier1-3 on AArch64 and x86_64 as well as Vector API tests on AArch64 SVE.
Add those vector api specific OPs to unsupported list for SVE.
This is a rebase of #3 to vectorIntrinsics.
Progress
Issue
Reviewers
Download
$ git fetch https://git.openjdk.java.net/panama-vector pull/7/head:pull/7
$ git checkout pull/7