-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Clear nested candidates in select if certainty is yes #141927
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
@bors2 try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
[PERF] Clear nested candidates in select if certainty is yes r? `@ghost`
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Finished benchmarking commit (c60b339): 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 the most reliable metric that we have; it was used to determine the overall result at the top of this comment. However, even this metric can sometimes exhibit noise.
Max RSS (memory usage)Results (secondary 0.1%)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 (secondary -0.7%)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: 743.192s -> 741.915s (-0.17%) |
47dbfcd
to
eba03a1
Compare
Minor perf improvement... r? lcnr |
Some changes occurred to the core trait solver cc @rust-lang/initiative-trait-system-refactor |
@@ -159,6 +160,12 @@ fn to_selection<'tcx>( | |||
}) | |||
.collect(); | |||
|
|||
// Drop nested goals from selection since they can't constrain the impl args | |||
// further if they're unambiguous. | |||
if let Ok(Certainty::Yes) = cand.result() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why not move this check higher up so that we don't even instantiate them if we've got Certainty::Yes
. I can imagine that only instantiating the opt impl args would give us another 1-2%
eba03a1
to
75b8312
Compare
@bors2 try parent=last @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
[PERF] Clear nested candidates in select if certainty is yes Proving these goals is redundant.
@bors2 try cancel |
Try build cancelled. Cancelled workflows: |
75b8312
to
a0971b8
Compare
@bors2 try parent=last @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
Finished benchmarking commit (95d796f): 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 the most reliable metric that we have; it was used to determine the overall result at the top of this comment. However, even this metric can sometimes exhibit noise.
Max RSS (memory usage)Results (primary -10.9%, secondary -1.0%)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 (secondary -1.0%)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: 743.192s -> 742.72s (-0.06%) |
seriously?? haha @bors try @rust-timer queue |
This comment has been minimized.
This comment has been minimized.
[PERF] Clear nested candidates in select if certainty is yes Proving these goals is redundant.
☀️ Try build successful - checks-actions |
This comment has been minimized.
This comment has been minimized.
1afd323
to
9f0e50c
Compare
Finished benchmarking commit (38419ce): 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 the most reliable metric that we have; it was used to determine the overall result at the top of this comment. However, even this metric can sometimes exhibit noise.
Max RSS (memory usage)Results (secondary -1.0%)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 (secondary -1.1%)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: 748.459s -> 749.441s (0.13%) |
let param_env = self.goal.goal.param_env; | ||
let mut orig_values = self.goal.orig_values.to_vec(); | ||
|
||
let mut opt_impl_args = None; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
vibeck:
change this to fn instantiate_impl_args
and eagerly return (after instantiating the final state + dealing with the term hack) if there's a inspect::ProbeStep::RecordImplArgs
and then unreachable!()
after the for
?
that is... something r=me after nit |
9f0e50c
to
1e5cd12
Compare
Not sure if this is exactly what u wanted, but I'd rather tweak this later since I want to land this. @bors r=lcnr rollup=never |
this isn't quite what I want, but we can merge and change it later myself 😁 |
☀️ Test successful - checks-actions |
What is this?This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.Comparing 5e0bdaa (parent) -> 2f2c8c3 (this PR) Test differencesNo test diffs found Test dashboardRun cargo run --manifest-path src/ci/citool/Cargo.toml -- \
test-dashboard 2f2c8c3512e82e4315db83bbb53eb79e2c566270 --output-dir test-dashboard And then open Job duration changes
How to interpret the job duration changes?Job durations can vary a lot, based on the actual runner instance |
Finished benchmarking commit (2f2c8c3): comparison URL. Overall result: ✅ improvements - no action needed@rustbot label: -perf-regression Instruction countThis is the most reliable metric that we have; it was used to determine the overall result at the top of this comment. However, even this metric can sometimes exhibit noise.
Max RSS (memory usage)Results (secondary 1.0%)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 (secondary -5.3%)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: 753.141s -> 752.958s (-0.02%) |
Proving these goals is redundant.