Vector algorithms: trim runtime coverage for ARM64EC non-vectorized fallbacks - #6142
Merged
Stephan T. Lavavej (StephanTLavavej) merged 7 commits intoMar 10, 2026
Conversation
Stephan T. Lavavej (StephanTLavavej)
approved these changes
Mar 6, 2026
Member
|
I'm mirroring this to the MSVC-internal repo. Please notify me if any further changes are pushed, otherwise no action is required. |
Stephan T. Lavavej (StephanTLavavej)
merged commit Mar 10, 2026
fab6100
into
microsoft:main
49 checks passed
Member
|
Thanks for keeping our test harness running efficiently! ⏱️ ✅ 😻 |
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
2 participants
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.
Follow up on #6107.
We can't have complexity in test matrices, especially for internal test runs, so let's trim the excess coverage otherwise.
I know it still adds some complexity in another place, so it is still controversial.
Trim random coverage, which is time-consuming, for the algorithms that are vectorized everywhere and don't have fallbacks.
After #6141, #6139, and #6143 this excludes all string algorithms. The following are left:
bitset,replace, andminmax_elementfor 64-bit integers and pointers.Deliberately avoided checking for
_VECTORIZED_*macros. We still need_USE_STD_VECTOR_ALGORITHMS=0coverage intact, and we need the machinery to be tested independently.