-
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
rustc_error, rustc_private: Switch to stable hash containers #99334
Conversation
r? @oli-obk (rust-highfive has picked a reviewer for you, use r? to override) |
Some changes occurred in src/tools/clippy cc @rust-lang/clippy |
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 865159dc76fa3721f1e0cf91d081c93ce8cbaa47 with merge b95c278d582803f03bad441057a05138712e2f25... |
☀️ Try build successful - checks-actions |
Queued b95c278d582803f03bad441057a05138712e2f25 with parent e1d9a20, future comparison URL. |
Finished benchmarking commit (b95c278d582803f03bad441057a05138712e2f25): 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 |
Looks like inlining noise?
|
What does this mean? That the heuristics governing inlining are triggering differently and creating noise in the benchmark? |
discussed in today's T-compiler triage meeting. That regression (to a single secondary benchmark I skimmed over it and it looks okay to me. So r=me once conflicts are resolved. |
@rustbot author |
yea, I have no idea what else it could be from that cachegrind run. I'd say we take the "hit". It may randomly unregress with other changes again. |
Sorry for forgetting about this PR. Please rebase and we'll send it off @bors rollup=never |
865159d
to
8d3c30c
Compare
No worries, I haven't been very active for a few months anyway. @rustbot ready |
@bors r+ |
⌛ Testing commit 8d3c30c with merge 5c6f92731524f08fc06fc677876ff0d23932f3fd... |
💔 Test failed - checks-actions |
@bors retry openssl timeout |
☀️ Test successful - checks-actions |
Finished benchmarking commit (52e003a): 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 |
…oli-obk rustc_error, rustc_private: Switch to stable hash containers Relates rust-lang#84447
Relates #84447