When the jdk.incubator.vector module is linked in a JDK image then the library libsvml.so is present and loaded in phase 2 of stub generation.

This occurs even if the jdk.incubator.vector module is not visible, since stub generation occurs before module definitions when the JVM boots. So we cannot predicate the library loading and stub generation on the UseVectorStubs flag.

This may cause conflicts with user applications using JNI that load (indirectly) libsvml.so distributed with Intel's MKL library.

For more details see:

https://mail.openjdk.java.net/pipermail/panama-dev/2021-October/015536.html

I have logged this against hotspot/runtime for now, but it may be some or all of the solution is build/infrastructure based e.g. we could rename the library.