Intrinsics code not linked out in Blazor sample

[CoffeeFlux]

When creating a new Blazor sample (dotnet new blazorwasm) and publishing in release, the linked corelib appears to still have lots of entries in System.Runtime.Intrinsics.*, which are kept around because of a call to System.Runtime.Intrinsics.Vector128. This appears to be used in Utf8Utility.GetPointerToFirstInvalidByte, but is guarded behind a call to AdvSimd.Arm64.IsSupported and ought to be linked out.

[vitek-karas]

This has been fixed in dotnet/runtime#43537. The fix didn't make 5.0 RTM. But in 6.0 it's there - I haven't validated by building against latest 6.0, but the code is missing from corelib in local build (so it won't be there when trimmed in an app).

[akoeplinger]

@vitek-karas I still see the intrinsics types in a linked System.Private.CoreLib.dll in dotnet/runtime using the wasm sample we have. Maybe it's being kept due to some other code path. It shouldn't need the 6.0 SDK right?

[akoeplinger]

the types only have the IsSupported property in them though. not sure if the linker should strip out those too?

[akoeplinger]

Hm looks like this is intentional: #1106

[marek-safar]

Only IsSupported calls should remain