[Mono] [Arm64] Add SIMD support for vector ctors

[jkurdek]

Should fix #97815

[ghost]

Tagging subscribers to this area: @SamMonoRT, @fanyang-mono
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Should fix #97815

Author:	jkurdek
Assignees:	-
Labels:	area-Codegen-Intrinsics-mono
Milestone:	-

[jkurdek]

/azp run runtime-extra-platforms

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[matouskozak]

LGTM, good job!
I noticed that there are System.Numerics.Vectors red on linux bionic arm64 but it looks infrastructure related. Possibly re-run of CI could make them green.

[jkurdek]

Checked some jobs before and after changes to vector3. System.Numerics.Vectors seems to be red on all of them, along with bunch of different tests on linux bionic arm64, I think it is not related.

[vargaz]

This seems to cause regressions on wasm:
https://dev.azure.com/dnceng-public/public/_build/results?buildId=556904&view=logs&jobId=b455efc5-4fe2-50ab-5106-412ad73c23a0&j=b455efc5-4fe2-50ab-5106-412ad73c23a0&t=607d8ddd-2371-58ff-95a3-14f9242e8c35

[vargaz]

Testcase:

using System;
using System.Threading.Tasks;
using System.Numerics;
using System.Runtime.Intrinsics;

public class Test
{
    public static void foo (Vector3 v) {
        var v2 = new Vector4 (v, 1.0f);
    }

    public static void Main () {
        foo (Vector3.Zero);
    }
}

The problems seems to be that the code emits a OP_INSERT_R4, but that expects sreg1 to be a simd vreg, but Vector3 right now is only marked as simd on arm64, not wasm, i.e. see init_class() in mini-runtime.c.

[jkurdek]

Yes, we do not have simd intrinsics for Vector2 and Vector3 on WASM. I'll create a PR disabling ctors simd on WASM.

[vargaz]

Adding a:

if (!mini_class_is_simd (cfg, mono_class_from_mono_type_internal (fsig->params [0])))
				// FIXME:
				return NULL;

to the Vector2/Vector3 cases should work around the problem.