-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Use assert_unchecked
instead of assume
intrinsic in the standard library
#119892
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
Conversation
r? @cuviper (rustbot has picked a reviewer for you, use r? to override) |
This comment has been minimized.
This comment has been minimized.
ee1dbce
to
fa9a911
Compare
Let's check since these are some perf-sensitive areas. @bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
…<try> Use `assert_unchecked` instead of `assume` intrinsic in the standard library Now that a public wrapper for the `assume` intrinsic exists, we can use it in the standard library. CC rust-lang#119131
☀️ Try build successful - checks-actions |
This comment has been minimized.
This comment has been minimized.
Finished benchmarking commit (c412b31): comparison URL. Overall result: ❌ regressions - no action neededBenchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. While you can manually mark this PR as fit for rollup, we strongly recommend not doing so since this PR may lead to changes in compiler perf. @bors rollup=never Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesThis benchmark run did not return any relevant results for this metric. Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 663.655s -> 664.42s (0.12%) |
Probably due to the additional IR having to be processed.. This seems fine to me though, the regression is really small on only two benchmarks. if wg-perf disagrees during triage, feel free to complain. |
…Nilstrieb Use `assert_unchecked` instead of `assume` intrinsic in the standard library Now that a public wrapper for the `assume` intrinsic exists, we can use it in the standard library. CC rust-lang#119131
This comment has been minimized.
This comment has been minimized.
💔 Test failed - checks-actions |
As nikic suggested, the codegen tests failed because debug-assertions are turned in some CI runners. They are now ignored in that case. |
@bors r=Nilstrieb,cuviper |
☀️ Test successful - checks-actions |
Finished benchmarking commit (e35a56d): comparison URL. Overall result: ❌ regressions - no action needed@rustbot label: -perf-regression Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesThis benchmark run did not return any relevant results for this metric. Binary sizeResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Bootstrap: 662.56s -> 662.94s (0.06%) |
Now that a public wrapper for the
assume
intrinsic exists, we can use it in the standard library.CC #119131