The <2 x f64> vector type is legal in the backend as a storage type
So the unpredicated load ad store instructions must support it.
Furthermore, the type can be used by the calling convention handling
machinery. A new test in mve-basic.ll specifically addresses this
case.
You've added patterns for v2f64, but are testing v16i8.
Why are we getting stack re-alignment code, when the alloca only has 8-byte alignment?