Following vector API tests are failing on E-Core Xeon targets where EnableX86EcoreOpts JVM runtime flag is enabled based on CPUID checks.



jdk/incubator/vector/Double256VectorTests.java: AssertionError: at index #0 expected [0.01] but found [0.009999992549419403]
jdk/incubator/vector/DoubleMaxVectorTests.java: AssertionError: at index #0 expected [0.01] but found [0.009999992549419403]
jdk/incubator/vector/Float128VectorTests.java: AssertionError: at index #1 expected [1.4E-45] but found [0.0]
jdk/incubator/vector/Float256VectorTests.java: AssertionError: at index #1 expected [1.4E-45] but found [0.0]
jdk/incubator/vector/FloatMaxVectorTests.java: AssertionError: at index #1 expected [1.4E-45] but found [0.0]
jdk/incubator/vector/Int128VectorTests.java: AssertionError: at index #2 expected [3] but found [1]
jdk/incubator/vector/Int256VectorTests.java: AssertionError: at index #1 expected [5] but found [4]
jdk/incubator/vector/IntMaxVectorTests.java: AssertionError: at index #1 expected [5] but found [4]
jdk/incubator/vector/Long256VectorTests.java: AssertionError: at index #0 expected [9223372036854775807] but found [9223372032559808511]
jdk/incubator/vector/LongMaxVectorTests.java: AssertionError: at index #0 expected [9223372036854775807] but found [9223372032559808511]


The problem looks related to variable blend emulation as these tests pass on P-core Xeon targets with -XX:UseAVX=2

Issue was reported by vladimir.a.ivanov@intel.com