-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Remove manual implementations of HashStable for hir::Expr and hir::Ty. #100237
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
Conversation
r? @nagisa (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 a72286a480993143f614f87b28557d90a5416b50 with merge 509af3ba830d34b1969e001c4d754a7297b9f868... |
This comment has been minimized.
This comment has been minimized.
a72286a
to
5d75ca5
Compare
The job Click to see the possible cause of the failure (guessed by this bot)
|
Looks like this PR still needs some work. @rustbot author |
@bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 5d75ca5 with merge d42a3b02aa87115fa1e5f89b27b0b6a98ff63d39... |
☀️ Try build successful - checks-actions |
Queued d42a3b02aa87115fa1e5f89b27b0b6a98ff63d39 with parent d394408, future comparison URL. |
Finished benchmarking commit (d42a3b02aa87115fa1e5f89b27b0b6a98ff63d39): 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 |
@bors r+ |
⌛ Testing commit 5d75ca5 with merge 54dcffb75444ece9bdc8e2822c57577949aac388... |
💔 Test failed - checks-actions |
@bors retry There is some kind of problem with GitHub Actions workflows being cancelled. |
☀️ Test successful - checks-actions |
Finished benchmarking commit (ef9810a): 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 |
We do not need to force hashing HIR bodies inside those nodes. The contents of bodies are not accessible from the
hir_owner
query which usedhash_without_bodies
. When the content of a body is required, the access is still done usinghir_owner_nodes
, which continues hashing HIR bodies.