-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
<vector>
: Fix ASan annotations when clear
ing
#2464
Merged
Merged
Conversation
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
cbezault
commented
Jan 10, 2022
miscco
reviewed
Jan 11, 2022
cbezault
changed the title
Jan 12, 2022
<vector>
: Correctly handle empty vectors with ASan annotations<vector>
: Fix ASan annotations when clear
ing
* Make `_Modify_annotation(0)` a safe no-op. + Add a comment explaining why. * Undo logic changes in `assign(n, val)` now that `_ASAN_VECTOR_MODIFY` is always safe. + There are no potential gains from calling `clear()` as this function begins by unconditionally calling `_My_data._Orphan_all();` and is required to do so by the Standard. * Comment `_ASAN_VECTOR_MODIFY` with `// negative when destroying elements` when subtracting pointers, making it clear that the order of operands is intentional. * Similarly, undo logic changes in `assign(i, j)` and `assign(il)`. They are also required to invalidate all iterators, so they can't benefit from `clear()`'s optimization here. * Ditto for `operator=(il)`. (The Standard isn't absolutely clear here, but behaving identically to `assign(il)` seems obviously good.) * Extend the `clear()` optimization to handle all empty vectors (zero size), not just zero capacity. + Add a comment explaining why, and citing the Standard for why this is allowed. * Similarly undo logic changes in `_Move_assign_unequal_alloc()`. * Add test coverage for calling `assign()` with an empty range of input iterators.
StephanTLavavej
approved these changes
Jan 13, 2022
I approve of Stephan's changes. |
CaseyCarter
approved these changes
Jan 13, 2022
I have mirrored this to MSVC-PR-373503 ( |
miscco
approved these changes
Jan 13, 2022
Thanks for clearing out this bug! 🐞 🪄 😸 |
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.
_Modify_annotation(0)
a no-op and add a comment explaining why: this avoids passingnullptr
into the ASan runtime when dealing with zero-capacity vectors._ASAN_VECTOR_MODIFY
with// negative when destroying elements
when subtracting pointers, making it clear that the order of operands is intentional.clear()
for empty vectors, and add a comment explaining why. This is permitted by the Standard, also explained in the comment.clear()
's use of_ASAN_VECTOR_MODIFY
.