improve performance of span_iterator w/ clang#1166
Merged
carsonRadtke merged 3 commits intomicrosoft:mainfrom Nov 12, 2024
Merged
improve performance of span_iterator w/ clang#1166carsonRadtke merged 3 commits intomicrosoft:mainfrom
carsonRadtke merged 3 commits intomicrosoft:mainfrom
Conversation
Member
Author
|
Benchmark details:
Benchmark results: #include <gsl/gsl>
#include <span>
template <typename T>
void foo(const T &sp) {
for (const auto &x : sp) {
}
}
auto gsl_foo = foo<gsl::span<int>>;
auto std_foo = foo<std::span<int>>;Before: After: |
Issue: #1165 Before this PR, the range-for loop was ~3300x slower. After this PR, it is ~1.005x slower The clang optimizer is very good at optimizing `current != end`, so we changed to this idiom. This moves the Expects assertion into the constructor instead of on the hot-path which is called whenever either operator++ or operator* is called. Note: The codegen for the assertion is still a missed optimization, but less worrisome as it only happens once per iterator. Note: benchmarks on M1 Macbook Pro w/ Apple Clang 16.0.0
42cfc54 to
898db79
Compare
Member
Author
More benchmarks (thanks to @galenelias). I'd like to see an improvement in It would also be nice to have performance regression tests (see #1165 (comment)). I will open an issue for this as well. |
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.
Issue: #1165
Before this PR, the range-for loop was ~3300x slower. After this PR, it is ~1.005x slower
The clang optimizer is very good at optimizing
current != end, so we changed to this idiom. This moves the Expects assertion into the constructor instead of on the hot-path which is called whenever either operator++ or operator* is called.Note: The codegen for the assertion is still a missed optimization, but less worrisome as it only happens once per iterator.