-
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
get rid of RefCell
in TransitiveRelation
#99702
Conversation
(rust-highfive has picked a reviewer for you, use r? to override) |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
d9f45cc
to
1a665aa
Compare
I'm not familiar with this area. |
This comment was marked as resolved.
This comment was marked as resolved.
please rebase so we can run a perf test on this. cc @lcnr this may conflict with your other refactorings |
I intend to add implied bounds to the param env so |
1a665aa
to
53dc99a
Compare
I add @oli-obk I rebased the PR so we can do a perf run now. |
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 53dc99a465b159eb13c3ac2ecd2924dfe65beab3 with merge d4e9c7f1d17ad93a14e06c762e2177954744128a... |
☀️ Try build successful - checks-actions |
Queued d4e9c7f1d17ad93a14e06c762e2177954744128a with parent ea6ab1b, future comparison URL. |
Finished benchmarking commit (d4e9c7f1d17ad93a14e06c762e2177954744128a): comparison url. Instruction count
Max RSS (memory usage)Results
CyclesResults
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. Benchmarking 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. Next Steps: If you can justify the regressions found in this try perf run, please indicate this with @bors rollup=never Footnotes |
Small perf changes:
mostly inlining changes (new_gen_kill -> into_engine) |
I add |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit d16796047523a6a17de08dcb739604f402526fb8 with merge e4ad27f1e1bd50aac91b50bd072257da970f393b... |
☀️ Try build successful - checks-actions |
Queued e4ad27f1e1bd50aac91b50bd072257da970f393b with parent 34805f3, future comparison URL. |
Finished benchmarking commit (e4ad27f1e1bd50aac91b50bd072257da970f393b): comparison url. Instruction count
Max RSS (memory usage)This benchmark run did not return any relevant results for this metric. CyclesResults
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. Benchmarking 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 Footnotes |
d167960
to
a01ac5a
Compare
@bors r+ |
Thanks for reviewing! |
☀️ Test successful - checks-actions |
Finished benchmarking commit (a8a33cf): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis benchmark run did not return any relevant results for this metric. 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.
CyclesResultsThis 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.
Footnotes |
This is one of the jobs in
Pending refactorings
in #48685. The parallel-compiler's work has been suspended for quite some time, but I think I can pick it up gradually. I think this PR should be a start.Regarding the refactoring of
TransitiveRelation
, @nikomatsakis has proposed two(three?) schemes. In order to satisfy both compilation efficiency and robustness, I think adding thefreeze
method may be the best solution, although it requires relatively more code changes.