8253211: Make sure jvm does not crash with Arm SVE and Vector API

[nsjian]

Add those vector api specific OPs to unsupported list for SVE.

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 patch also fixed one missing VectorA handling in previous merge.

---

Progress

• Change must not contain extraneous whitespace
• Commit message must refer to an issue
• Change must be properly reviewed

Issue

• JDK-8253211: Make sure jvm does not crash with Arm SVE and Vector API

Reviewers

• Vladimir Ivanov (@iwanowww - Reviewer)

Download

$ git fetch https://git.openjdk.java.net/panama-vector pull/3/head:pull/3
$ git checkout pull/3

[bridgekeeper]

👋 Welcome back njian! A progress list of the required criteria for merging this PR into vector-unstable will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[mlbridge]

Webrevs

• 00: Full (aac5213)

[iwanowww]

Looks good.

[openjdk]

@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:

8253211: Make sure jvm does not crash with Arm SVE and Vector API

Reviewed-by: vlivanov

• If you would like to add a summary, use the /summary command.
• To credit additional contributors, use the /contributor command.
• To add additional solved issues, use the /issue command.

There are currently no new commits on the vector-unstable branch since the last update of the source branch of this PR. If another commit should be pushed before you perform the /integrate command, your PR will be automatically rebased. If you would like to avoid potential automatic rebasing, specify the current head hash when integrating, like this: /integrate 95cd392cf34469db4d5dbc8fbca28008797225cf.

➡️ To integrate this PR with the above commit message to the vector-unstable branch, type /integrate in a new comment.

[PaulSandoz]

Can you please rebase to the vectorIntrinsics branch? We are trying to keep vector-unstable stable :-) for integration into jdk. After that we can then take changes to vectorIntrinsics directly to jdk.

[mlbridge]

Mailing list message from Vladimir Ivanov on panama-dev:

Can you please rebase to the `vectorIntrinsics` branch? We are trying to keep `vector-unstable` stable :-) for
integration into `jdk`. After that we can then take changes to `vectorIntrinsics` directly to `jdk`.

Good point! I completely missed that the PR is against vector-unstable :-)

Best regards,
Vladimir Ivanov

[nsjian]

Can you please rebase to the vectorIntrinsics branch? We are trying to keep vector-unstable stable :-) for integration into jdk. After that we can then take changes to vectorIntrinsics directly to jdk.

Without this patch, jvm will crash on SVE with Vector API, so I want to get this into 'vector-unstable' for integration into jdk. Do you think it make sense? Current vectorIntrinsics is a bit behind vector-unstable and jdk/jdk, e.g. without Arm SVE support yet, so this patch cannot apply to vectorIntrinsics. We need to merge vector-unstable into vectorIntrinsics first.

[PaulSandoz]

@nsjian Is it possible for you to send a pull request to merge master with vectorIntrinsics, and then a second pull request for this to vectorIntrinsics?

I don't want to add anything to vector-unstable, except merge updates, that might cause a re-review of code. When i send the pull request for integration i want to state accurately that the code was already reviewed (if we were still using mercurial we could just push directly). It should be possible to quickly follow up after the initial integration.

[nsjian]

@nsjian Is it possible for you to send a pull request to merge master with vectorIntrinsics, and then a second pull request for this to vectorIntrinsics?

Sure, I will give a try.

I don't want to add anything to vector-unstable, except merge updates, that might cause a re-review of code. When i send the pull request for integration i want to state accurately that the code was already reviewed (if we were still using mercurial we could just push directly). It should be possible to quickly follow up after the initial integration.

OK, that's fine to me.