-
Notifications
You must be signed in to change notification settings - Fork 13k
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
Pass Context as a &mut to allow to remove RefCell fields #97433
Conversation
Let's check perf impact. @bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 4ae06b6c9d3fd193ba079e2354db6ab0cf3abf3a with merge 942977e8897f606274245db5bc087d364636c2f7... |
How can this work if #82741 parallel rustdoc is implemented? |
It won't but they needed to be updated in any case. |
☀️ Try build successful - checks-actions |
Queued 942977e8897f606274245db5bc087d364636c2f7 with parent 1851f08, future comparison URL. |
It's a good point. Hopefully passing Context as |
Finished benchmarking commit (942977e8897f606274245db5bc087d364636c2f7): 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. @bors rollup=never Footnotes |
It seems to be slower for a lower memory usage. Is it worth it to merge it then? |
Hold on a second, something is wrong here. All 3 regressions are in check builds, not doc. They can't be related to this change. |
You're right! Doc builds are mostly the same apparently. |
@bors delegate+ |
✌️ @GuillaumeGomez can now approve this pull request |
4ae06b6
to
6ab8edb
Compare
I applied suggestions. Let's see if the perf check result is different this time. @bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 6ab8edb with merge 0f677d3ec04c23ef97068ac3aa0a72820aa2cc35... |
☀️ Try build successful - checks-actions |
Queued 0f677d3ec04c23ef97068ac3aa0a72820aa2cc35 with parent 56fd680, future comparison URL. |
Finished benchmarking commit (0f677d3ec04c23ef97068ac3aa0a72820aa2cc35): comparison url. Instruction countThis benchmark run did not return any relevant results for this metric. 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. @bors rollup=never Footnotes |
@bors r+ |
📌 Commit 6ab8edb has been approved by |
Neither of the proclaimed "max-rss regressions" are even on |
☀️ Test successful - checks-actions |
Finished benchmarking commit (764b861): 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. @rustbot label: -perf-regression Footnotes |
Fixes #90323.
r? @notriddle