refactor: memcpy to std::ranges::copy to work around ubsan warn#305
Open
maflcko wants to merge 1 commit into
Open
refactor: memcpy to std::ranges::copy to work around ubsan warn#305maflcko wants to merge 1 commit into
maflcko wants to merge 1 commit into
Conversation
|
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers. ReviewsSee the guideline and AI policy for information on the review process.
If your review is incorrectly listed, please copy-paste |
d4b028b to
fac7b9b
Compare
Contributor
Author
|
Failure should look roughly like: |
Member
|
Concept ACK on replacing |
Member
|
ACK fac7b9b I was also able to reproduce the error that the new test triggers. |
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.
Using std::ranges::copy from the C++ standard library has a few benefits here:
This should also fix bitcoin/bitcoin#35118 (comment)