Repository navigation
Enable opt-in Windows AVX2 builds with MSVC - #326
Open
edkazcarlson wants to merge 3 commits into
Open
edkazcarlson wants to merge 3 commits into
edkazcarlson wants to merge 3 commits into
Conversation
This branch has not been deployed
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Enable opt-in Windows AVX2 builds with MSVC
PR base:
main. The Windows workflow previously bypassed the repository's SIMDoptions, and enabling its AVX option with native MSVC encountered GCC alignment
syntax. This change supplies compatible alignment declarations and a shared
PowerShell build entrypoint, with default and AVX2 CI configurations.
The published DLL retains its existing compiler target.
-Simd avx2opts intoboth AVX floating-point and AVX2 Hamming code, requiring compatible hardware.
There is no new runtime dispatcher, dependency, SQL API, FP16 code, or package.
This follows the existing compile-time SIMD convention. The workflow artifact
names distinguish the test configurations; release artifact names are unchanged.