Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[WASM] PackedSimd.IsSupported returns false in .NET 8.0.11~9.0.0 #111085

Open
zyl910 opened this issue Jan 4, 2025 · 1 comment
Open

[WASM] PackedSimd.IsSupported returns false in .NET 8.0.11~9.0.0 #111085

zyl910 opened this issue Jan 4, 2025 · 1 comment
Labels
area-Codegen-Intrinsics-mono os-browser Browser variant of arch-wasm untriaged New issue has not been triaged by the area owner

Comments

@zyl910
Copy link

zyl910 commented Jan 4, 2025

Description

On .NET 8.0.7, the Blazor WASM project has SIMD hardware acceleration. Both Vector128.IsHardwareAccelerated and PackedSimd.IsSupported return true.

.NET was updated to version 8.0.11 after the Visual Studio 2022 upgrade. The SIMD hardware acceleration of the WASM project is not work. Both Vector128.IsHardwareAccelerated and PackedSimd.IsSupported return false.

Changed the target framework of the project to net 9.0, still no SIMD hardware acceleration. Both Vector128.IsHardwareAccelerated and PackedSimd.IsSupported return false.

Tested on Edge, Chrome, and Firefox browsers with the same results.

Log from .NET 8.0.7

RuntimeInformation.FrameworkDescription:	.NET 8.0.7
RuntimeInformation.OSArchitecture:	Wasm
RuntimeInformation.OSDescription:	Browser
RuntimeInformation.RuntimeIdentifier:	browser-wasm
Vector128.IsHardwareAccelerated:	True
PackedSimd.IsSupported:	True

Log from .NET 8.0.11

RuntimeInformation.FrameworkDescription:	.NET 8.0.11
RuntimeInformation.OSArchitecture:	Wasm
RuntimeInformation.OSDescription:	Browser
RuntimeInformation.RuntimeIdentifier:	browser-wasm
Vector128.IsHardwareAccelerated:	False
PackedSimd.IsSupported:	False

Reproduction Steps

From a Standalone Blazor WASM project starting on 8.0.7, compile and run. Then, upgrade to 8.0.11/9.0.0 and try again.

Expected behavior

Vector128.IsHardwareAccelerated = true
PackedSimd.IsSupported = true

Actual behavior

Vector128.IsHardwareAccelerated = false
PackedSimd.IsSupported = false

Regression?

No response

Known Workarounds

No response

Configuration

.NET Version: 8.0.11/9.0.0
OS: Windows 11 24H2 build 26100.2605
Architecture: x64
CPU: AMD Ryzen 7 7840H

Browsers:

  • Edge 131
  • Chrome 131
  • FireFox 2023.6

dotnet --info:

.NET SDK:
 Version:           9.0.101
 Commit:            eedb237549
 Workload version:  9.0.100-manifests.4a280210
 MSBuild version:   17.12.12+1cce77968

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.26100
 OS Platform: Windows
 RID:         win-x64
 Base Path:   C:\Program Files\dotnet\sdk\9.0.101\

.NET workloads installed:
 [wasm-tools-net8]
   Installation Source: VS 17.12.35527.113
   Manifest Version:    9.0.0/9.0.100
   Manifest Path:       C:\Program Files\dotnet\sdk-manifests\9.0.100\microsoft.net.workload.mono.toolchain.net8\9.0.0\WorkloadManifest.json
   Install Type:              Msi

Other information

No response

@dotnet-issue-labeler dotnet-issue-labeler bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Jan 4, 2025
@dotnet-policy-service dotnet-policy-service bot added the untriaged New issue has not been triaged by the area owner label Jan 4, 2025
@huoyaoyuan huoyaoyuan added area-Codegen-Intrinsics-mono os-browser Browser variant of arch-wasm and removed needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners labels Jan 4, 2025
Copy link
Contributor

Tagging subscribers to this area: @steveisok, @vitek-karas
See info in area-owners.md if you want to be subscribed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-Codegen-Intrinsics-mono os-browser Browser variant of arch-wasm untriaged New issue has not been triaged by the area owner
Projects
None yet
Development

No branches or pull requests

2 participants