compiler: update hashbrown to 0.17

[cuviper]

See library's #155154 for the bug fixes this brings.
This PR also updates indexmap in the compiler as a direct dependent.

[rustbot]

These commits modify the Cargo.lock file. Unintentional changes to Cargo.lock can be introduced when switching branches and rebasing PRs.

If this was unintentional then you should revert the changes before this PR is merged.
Otherwise, you can ignore this comment.

[rustbot]

r? @Mark-Simulacrum

rustbot has assigned @Mark-Simulacrum.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

Why was this reviewer chosen?

The reviewer was selected based on:

• Owners of files modified in this PR: @Mark-Simulacrum

[rustbot]

⚠️ Warning ⚠️

• There are issue links (such as #123) in the commit messages of the following commits.
  Please move them to the PR description, to avoid spamming the issues with references to the commit, and so this bot can automatically canonicalize them to avoid issues with subtree.
  • 6e618be

[Mark-Simulacrum]

@bors try @rust-timer queue

At some point we should chase down the other sources of older deps as well:

$ cargo tree -i hashbrown@0.16.1 --depth 1
hashbrown v0.16.1
└── indexmap v2.13.0

hashbrown v0.16.1
├── indexmap v2.13.0
├── rustc_data_structures v0.0.0 (compiler/rustc_data_structures)
├── wasmparser v0.246.2
└── wit-parser v0.246.2

$ cargo tree -i hashbrown@0.15 --depth 1
hashbrown v0.15.5
├── object v0.36.7
├── object v0.37.3
└── thorin-dwp v0.9.0

[rust-bors]

☀️ Try build successful (CI)
Build commit: 110c0e2 (110c0e2412ed37d74fb75f3bc12e379661dd5247, parent: 17584a181979f04f2aaad867332c22db1caa511a)

[rust-timer]

Finished benchmarking commit (110c0e2): comparison URL.

Overall result: no relevant changes - no action needed

Benchmarking means the PR may be perf-sensitive. It's automatically marked not fit for rolling up. Overriding is possible but disadvised: it risks changing compiler perf.

@bors rollup=never
@rustbot label: -S-waiting-on-perf -perf-regression

Instruction count

This perf run didn't have relevant results for this metric.

Max RSS (memory usage)

Results (primary 2.1%, secondary -4.5%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

	mean	range	count
Regressions ❌ (primary)	2.1%	[2.1%, 2.1%]	1
Regressions ❌ (secondary)	-	-	0
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-4.5%	[-4.5%, -4.5%]	1
All ❌✅ (primary)	2.1%	[2.1%, 2.1%]	1

Cycles

This perf run didn't have relevant results for this metric.

Binary size

This perf run didn't have relevant results for this metric.

Bootstrap: 489.468s -> 491.134s (0.34%)
Artifact size: 394.17 MiB -> 394.18 MiB (0.00%)

[Mark-Simulacrum]

@bors r+

[rust-bors]

📌 Commit 6e618be has been approved by Mark-Simulacrum

It is now in the queue for this repository.

[rust-bors]

💔 Test for 68e557c failed: CI. Failed job:

• auto - x86_64-gnu-llvm-21 (web logs, enhanced plaintext logs)

[rust-log-analyzer]

The job x86_64-gnu-llvm-21 failed! Check out the build log: (web) (plain enhanced) (plain)

Click to see the possible cause of the failure (guessed by this bot)

[TIMING:end] compile::StdLink { compiler: Compiler { stage: 0, host: x86_64-unknown-linux-gnu, forced_compiler: false }, target_compiler: Compiler { stage: 0, host: x86_64-unknown-linux-gnu, forced_compiler: false }, target: x86_64-unknown-linux-gnu, crates: [], force_recompile: false } -- 0.002
##[group]Building stage1 compiler artifacts (stage0 -> stage1, x86_64-unknown-linux-gnu)
error: process didn't exit successfully: `sccache /checkout/obj/build/bootstrap/debug/rustc -vV` (exit status: 2)
--- stderr
sccache: error: Timed out waiting for server startup. Maybe the remote service is unreachable?
Run with SCCACHE_LOG=debug SCCACHE_NO_DAEMON=1 to get more information

Bootstrap failed while executing `--stage 2 test tests/mir-opt --host= --target=i686-unknown-linux-gnu`
Build completed unsuccessfully in 0:00:17
  local time: Wed Apr 15 00:42:19 UTC 2026
  network time: Wed, 15 Apr 2026 00:42:19 GMT

[JonathanBrouwer]

@bors retry
Spurious

[rust-bors]

☀️ Test successful - CI
Approved by: Mark-Simulacrum
Duration: 3h 19m 16s
Pushing 32e4c0e to main...

[github-actions]

What is this?

This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.

Comparing 57cb10a (parent) -> 32e4c0e (this PR)

Test differences

Show 3 test diffs

3 doctest diffs were found. These are ignored, as they are noisy.

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard 32e4c0ecbd046aafdde22043b2fb7b205587c5f6 --output-dir test-dashboard

And then open test-dashboard/index.html in your browser to see an overview of all executed tests.

Job duration changes

1. aarch64-apple: 3h 47m -> 2h 26m (-35.6%)
2. x86_64-gnu-miri: 1h 36m -> 1h 8m (-29.0%)
3. x86_64-gnu-llvm-22-2: 1h 17m -> 1h 38m (+26.2%)
4. x86_64-gnu-aux: 1h 51m -> 2h 20m (+26.2%)
5. dist-apple-various: 1h 44m -> 2h 11m (+25.6%)
6. dist-x86_64-netbsd: 1h 11m -> 1h 26m (+20.9%)
7. dist-x86_64-freebsd: 1h 23m -> 1h 9m (-16.4%)
8. dist-ohos-x86_64: 1h 6m -> 1h 16m (+14.4%)
9. x86_64-mingw-1: 2h 43m -> 3h 6m (+14.1%)
10. test-various: 1h 57m -> 2h 9m (+11.0%)

How to interpret the job duration changes?

Job durations can vary a lot, based on the actual runner instance
that executed the job, system noise, invalidated caches, etc. The table above is provided
mostly for t-infra members, for simpler debugging of potential CI slow-downs.

[rust-timer]

Finished benchmarking commit (32e4c0e): comparison URL.

Overall result: no relevant changes - no action needed

@rustbot label: -perf-regression

Instruction count

This perf run didn't have relevant results for this metric.

Max RSS (memory usage)

Results (primary 1.9%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

	mean	range	count
Regressions ❌ (primary)	1.9%	[1.9%, 1.9%]	1
Regressions ❌ (secondary)	-	-	0
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-	-	0
All ❌✅ (primary)	1.9%	[1.9%, 1.9%]	1

Cycles

Results (primary 2.0%, secondary -2.5%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

	mean	range	count
Regressions ❌ (primary)	2.0%	[2.0%, 2.0%]	1
Regressions ❌ (secondary)	-	-	0
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-2.5%	[-2.5%, -2.5%]	1
All ❌✅ (primary)	2.0%	[2.0%, 2.0%]	1

Binary size

This perf run didn't have relevant results for this metric.

Bootstrap: 489.055s -> 490.627s (0.32%)
Artifact size: 394.13 MiB -> 394.10 MiB (-0.01%)