-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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
rustdoc: Remove Crate.externs
and compute on-demand instead
#91066
Conversation
This will allow removing `Crate.externs`.
This comment has been minimized.
This comment has been minimized.
It populates `cx.cache.access_levels`, which seems to be needed during cleaning since a bunch of tests are failing.
@bors rollup=never |
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit bbc3825 with merge fa4bd5e2d3e9a77104d23aef85b2d36578b94eb3... |
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.
Lol you'd already fixed my one comment by the time I finished the review, nice
Anyway, this looks good whether or not it's a perf improvement, r=me |
☀️ Try build successful - checks-actions |
Queued fa4bd5e2d3e9a77104d23aef85b2d36578b94eb3 with parent a77da2d, future comparison URL. |
Finished benchmarking commit (fa4bd5e2d3e9a77104d23aef85b2d36578b94eb3): comparison url. Summary: This change led to large relevant regressions 😿 in compiler performance.
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 led 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 |
It seems like it doesn't impact performance or memory usage. I'm a bit surprised but doesn't matter. Thanks for the simplification! @bors: r=jyn514,GuillaumeGomez |
📌 Commit bbc3825 has been approved by |
☀️ Test successful - checks-actions |
Finished benchmarking commit (93542a8): comparison url. Summary: This benchmark run did not return any relevant changes. If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression |
It looks like this is probably the cause of a regression. See #91134. |
Update from that issue: the regression is likely from somewhere else. |
r? @GuillaumeGomez
cc @jyn514