[vector-unstable] RFR: 8253211: Make sure jvm does not crash with Arm SVE and Vector API

[Paul Sandoz]

On Thu, 17 Sep 2020 01:36:24 GMT, Ningsheng Jian <njian at openjdk.org> wrote:

>> 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`.
>
>> 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.

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

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

PR: https://git.openjdk.java.net/panama-vector/pull/3