-
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
cache collect_trait_impl_trait_tys
#101787
Conversation
(rust-highfive has picked a reviewer for you, use r? to override) |
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 2ef3958fd09e9bbc03e8d38fb8afc7209dfc37bd with merge 379426e81938234c83195c9eb29e036e6c116da3... |
Shouldn't have much/any perf effect on non-RPITIT (return-position |
This comment has been minimized.
This comment has been minimized.
☀️ Try build successful - checks-actions |
Queued 379426e81938234c83195c9eb29e036e6c116da3 with parent 88a1922, future comparison URL. |
Finished benchmarking commit (379426e81938234c83195c9eb29e036e6c116da3): comparison URL. Overall result: no relevant changes - 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 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 |
No difference it seems. |
2ef3958
to
4cdf264
Compare
@petrochenkov I actually expected this to show no improvements, just wanted to double check this showed no regressions for code that didn't use these queries (but also I didn't expect any). This will probably be a significant improvement for incremental code that does use return-position I would still like to land this though, since it's along the same lines as caching the @rustbot ready |
Ok, I see. |
…trochenkov cache `collect_trait_impl_trait_tys` Micro-optimization for RPITITs
…trochenkov cache `collect_trait_impl_trait_tys` Micro-optimization for RPITITs
…trochenkov cache `collect_trait_impl_trait_tys` Micro-optimization for RPITITs
Rollup of 7 pull requests Successful merges: - rust-lang#101722 (Rustdoc-Json: Fix Type docs.) - rust-lang#101738 (Fix `#[link kind="raw-dylib"]` to respect `#[link_name]`) - rust-lang#101753 (Prefer explict closure sig types over expected ones) - rust-lang#101787 (cache `collect_trait_impl_trait_tys`) - rust-lang#101802 (Constify impl Fn* &(mut) Fn*) - rust-lang#101809 (Replace `check_missing_items.py` with `jsondoclint`) - rust-lang#101864 (rustdoc: remove no-op CSS `h1-4 { color: --main-color }`) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
Micro-optimization for RPITITs