-
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
Upgrade indexmap and thorin-dwp to use hashbrown 0.12 #99251
Conversation
Some changes occurred in compiler/rustc_codegen_cranelift cc @bjorn3 |
(rust-highfive has picked a reviewer for you, use r? to override) |
just the usual sanity check: @bors try @rust-timer queue |
Awaiting bors try build completion. @rustbot label: +S-waiting-on-perf |
⌛ Trying commit 8dece5c37a154df71fc5ddbe971d975f9b70e610 with merge 1d7eef78297735725da8f0383f19fcb93167f60d... |
☀️ Try build successful - checks-actions |
Queued 1d7eef78297735725da8f0383f19fcb93167f60d with parent b90a0ed, future comparison URL. |
Finished benchmarking commit (1d7eef78297735725da8f0383f19fcb93167f60d): 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 |
looks like usual ctfe-stress-5 noise. r=me rollup=never if you agree |
@bors r+ Yeah, seems like it. Nice improvement in bootstrap times as well! |
📌 Commit 8dece5c37a154df71fc5ddbe971d975f9b70e610 has been approved by It is now in the queue for this repository. |
Indeed, the |
This removes the last dependencies on hashbrown 0.11.
This fixes a double-free in the `clone_from` function if dropping an existing element in the table panics. See rust-lang/hashbrown#348 for more details.
@bors r+ rollup=never @Amanieu Do we have a reference for when the double-drop was introduced into hashbrown? I would've expected to see that in the changelog entry (https://github.com/rust-lang/hashbrown/blob/master/CHANGELOG.md#v0123---2022-07-17), at least, but it doesn't seem to be there. Has it always been there? |
I think it's always been there. |
☀️ Test successful - checks-actions |
Finished benchmarking commit (4dbc89d): 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. Next Steps: If you can justify the regressions found in this perf run, please indicate this with @rustbot label: +perf-regression Footnotes |
beta-nominating this PR; this addresses a soundness problem in hashbrown (double-free in clone_from) which seems good to roll out to stable on a faster schedule. |
…crum Upgrade indexmap and thorin-dwp to use hashbrown 0.12 This removes the last dependencies on hashbrown 0.11. This also upgrades to hashbrown 0.12.3 to fix a double-free (rust-lang#99372).
…mulacrum [beta] Rollup of beta backports Includes the following PRs: * rustc-docs: Be less specific about the representation of +bundle rust-lang#100074 * Fix backwards-compatibility check for tests with +whole-archive rust-lang#100068 * Revert write! and writeln! to late drop temporaries rust-lang#99689 * Upgrade indexmap and thorin-dwp to use hashbrown 0.12 rust-lang#99251 * rustdoc: avoid inlining modules with duplicate names rust-lang#99738 r? `@ghost`
This removes the last dependencies on hashbrown 0.11.
This also upgrades to hashbrown 0.12.3 to fix a double-free (#99372).