-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
[perf] skip normalizing param env if it is already normalized #130561
Conversation
@bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
[perf] skip normalizing param env if it is already normalized If the param env is already normalized after elaboration, then we can skip a bunch of expensive operations. > [!note] > This makes it so that outlives predicates are no longer sorted after non-outlives predicates. Surely this won't make a semantic difference. r? ghost
☀️ Try build successful - checks-actions |
This comment has been minimized.
This comment has been minimized.
Finished benchmarking commit (8670a07): comparison URL. Overall result: ✅ improvements - 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)Results (primary -1.2%, secondary -0.2%)This 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.
CyclesResults (primary -2.3%, secondary -3.8%)This 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.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 769.526s -> 768.035s (-0.19%) |
👍 AFAICT, we should not have order dependence for our type outlives obligations at least; I double checked lexical region resolution and MIR borrowck and nothing seemed suspicious there. Or at least, we certainly don't have any order dependence between type-outlives and other predicates. @bors r+ |
☀️ Test successful - checks-actions |
Finished benchmarking commit (5793a9e): comparison URL. Overall result: ✅ improvements - 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)Results (primary -1.6%, secondary -0.6%)This 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.
CyclesResults (primary -2.3%, secondary -2.4%)This 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.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 768.807s -> 768.735s (-0.01%) |
If the param env is already normalized after elaboration, then we can skip a bunch of expensive operations.
Note
This makes it so that outlives predicates are no longer sorted after non-outlives predicates. Surely this won't make a semantic difference.
r? ghost