Revert product changes for find_end vectorization#5041
Merged
StephanTLavavej merged 1 commit intomicrosoft:mainfrom Oct 26, 2024
Merged
Conversation
This was GH 4943.
CaseyCarter
approved these changes
Oct 25, 2024
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
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.
After we merged #4943 (
find_endvectorization), @CaseyCarter noticed that the STL-ASan-CI began failing with container-overflow errors.This reverts the product code changes from #4943 but allows its benchmark and test changes to stand. It also keeps a control flow refactoring of
__std_search_implinstl/src/vector_algorithms.cpp, as I'm convinced it's a lossless transformation.🙀 Test Failure Log
This can be found by downloading a test failure log as an XML artifact, then running my
tools\scripts\print_failures.pyto decode it. (Thanks again @CaseyCarter for noticing that the artifact captured the log, which was too big for the usual Azure Pipelines UI to display.)Click to expand test failure log:
✅ ASan Validation Incantations
Here's how to build the STL with ASan enabled (
-DSTL_ASAN_BUILD=ON), then run the test with ASan enabled (-Dtags=ASAN):