Open neon-sunset opened 1 month ago
For Vector<T>
you need to play with DOTNET_MaxVectorTBitWidth
env var. Although, I agree that UX is not great, DOTNET_PreferredVectorBitWidth=128
should probably also changer Vector<T>
cc @tannergooding
Tagging subscribers to this area: @dotnet/area-system-numerics See info in area-owners.md if you want to be subscribed.
Description
It appears that
Vector<T>
matches native vector width regardless of the value specified in environment variableDOTNET_PreferredVectorBitWidth
.Reproduction Steps
Given
dotnet run -c Release
and the following code:Expected behavior
none
$env:DOTNET_PreferredVectorBitWidth=128
Actual behavior
none
$env:DOTNET_PreferredVectorBitWidth=128
Regression?
Doesn't seem so
Known Workarounds
Disable platform-specific ISA with e.g.
DOTNET_EnableAVX=0
.Configuration
Other information
No response