Migrate to core::hint::black_box()
#16980
Open
+48
−23
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.
Objective
Many of our benchmarks use
criterion::black_box()
, which is used to prevent the compiler from optimizing away computation that we're trying to time. This can be slow, though, becausecriterion::black_box()
forces a point read each time it is called throughptr::road_volatile()
.In Rust 1.66, the standard library introduced
core::hint::black_box()
(andstd::hint::black_box()
). This is an intended replacement forcriterion
's version that uses compiler intrinsics instead of volatile pointer reads, and thus has no runtime overhead. This increases benchmark accuracy, which is always nice 👍Note that benchmarks may appear to improve in performance after this change, but that's just because we are eliminating the pointer read overhead.
Solution
criterion::black_box
inclippy.toml
.Testing
cargo clippy -p benches --benches