-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Allow the user to control the MaxVectorTBitWidth (#85551)
* Expose DOTNET_MaxVectorTBitWidth and an undocumented DOTNET_PreferredVectorBitWidth * Ensure SPMI keeps a getMaxVectorTBitWidth implementation * Fix the non-xarch vm build * Remove getMaxVectorTBitWidth from the JIT/EE interface, it's no longer needed * Move SetCpuInfo down into the EEJitManager constructor * Remove getXarchCpuInfo in favor of passing `JIT_FLAG_VECTOR512_THROTTLING` * Make sure CORINFO_XARCH_CPU is fully removed * Have ENCODE_VERIFY_TYPE_LAYOUT not fail-fast for Vector<T> size differences * Only encode types containing Vector<T> as check, not verify * Remove changes that were extracted to separate PRs * Ensure that the optimistic flags are a strict superset of the supported flags * Make VectorT128/256/512 proper instruction sets and only allow one to be active at a time * Don't allow avxvnni to be "optimistic" since that brings in avx2 * Ensure we handle HWIntrinsics being disabled * Ensure that the Vector<T> size ISAs are covered by FromInstructionSet * Ensure that `getMaxVectorByteLength` being 0 is handled * Ensure NAOT startup can correctly check for the VectorT size bits * Have BlkOpKindUnroll account for SIMD being disabled * Ensure InstructionSet_VectorT128 is set in the fallback path for PAL_GetJitCpuCapabilityFlags
- Loading branch information
1 parent
6328b23
commit af1262c
Showing
42 changed files
with
651 additions
and
269 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.