[libc++] Optimize ranges::move{,_backward} for vector<bool>::iterator #121109
+362
−110
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
winner245
force-pushed
the
optimize-ranges-move
branch
3 times, most recently
from
544adcf to
cd7a802
Compare
winner245
force-pushed
the
optimize-ranges-move
branch
from
cd7a802 to
6d84599
Compare
winner245
force-pushed
the
optimize-ranges-move
branch
from
6d84599 to
dc159bd
Compare
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.
As a follow-up to #121013 (which optimized
ranges::copy) and #121026 (which optimizedranges::copy_backward), this PR enhances the performance ofstd::ranges::{move, move_backward}forvector<bool>::iterator, addressing a subtask outlined in issue #64038.The optimizations bring performance improvements analogous to those achieved for the
{copy, copy_backward}algorithms: up to x for aligned moves and x for unaligned moves.