Appears Blazor SIMD builds now work on non-SIMD architecture - need confirmation

[Sean4572435243]

I have a standalone Blazor webassembly app that I have two builds for, SIMD and non-SIMD. The user's browser will attempt to load the SIMD version first, but if encountering compatibility errors, it will fail over to the non-SIMD version. After recent upgrades to 9.0.3 (possibly prior), or due to Window 11 updates, or due to Chromium updates, it now appears that the SIMD build executes on non-SIMD architecture.

I am not certain if this was an intentional evolution that I can safely assume non-SIMD builds are no longer necessary, or if I should continue maintaining the dual-build approach. Some clarification would be most appreciated.

[lewing]

what version of chrome and what architecture?

[Sean4572435243]

Chrome 134.0.6998.89 (Official Build) (64-bit) in
Hyper-V Windows 11 (updated to latest)
Host OS Name Microsoft Windows Server 2012 R2 Standard
Host OS Version 6.3.9600 Build 9600
Server hardware is at least a 7 year old Atom CPU/board, as follows
System Manufacturer Supermicro
System Model Super Server
Processor Intel(R) Atom(TM) CPU C3850 @ 2.10GHz, 2100 Mhz, 12 Core(s), 12 Logical Processor(s)

certainly not SIMD compatible, which is why I was employing the dual-build strategy. This incompatibility permeated into all Hyper-V instances since it's based on the CPU, not OS. This leads me to believe that the latest Blazor or latest Chrome is smart enough to check SIMD compatibility, and executes the appropriate variation of code instead of blowing up like it has historically.

Hoping to understand how this seeming compatibility has been accomplished to determine whether I need to maintain dual builds going forward.