Update cargo submodule

[weihanglo]

9 commits in b2e9d5f9db3fb1c454ab84f10c16508984a266e2..3c0b534756e166d12eb9fd2e1abfe5b42ac6101e
2026-09-02 14:49:16 +0000 to 2026-09-04 17:03:10 +0000

• fix(trim-paths)!: limit options to none|object|all (fix(trim-paths)!: limit options to none|object|all cargo#17432)
• fix(git): Apply pr hint to git-fetch-with-cli (fix(git): Apply pr hint to git-fetch-with-cli cargo#17437)
• fix(git): Make PR dep note cloer to our style guide (fix(git): Make PR dep note cloer to our style guide cargo#17436)
• docs: clarify cargo vendor source config option (docs: clarify cargo vendor source config option cargo#17435)
• docs(trim-paths): workspace remap begins with . (docs(trim-paths): workspace remap begins with . cargo#17433)
• docs: Switch from "target triple" to "target tuple" (docs: Switch from "target triple" to "target tuple" cargo#17430)
• docs(trim-paths): add limitations and polish (docs(trim-paths): add limitations and polish cargo#17425)
• fix(git): Simplify error message (fix(git): Simplify error message cargo#17429)
• chore(deps): update rust crate base64 to 0.23.0 (chore(deps): update rust crate base64 to 0.23.0 cargo#17418)

[rustbot]

⚠️ Warning ⚠️

• Some commits in this PR modify submodules.

  If this was not intentional, see I changed a submodule on accident in the rustc dev guide.

[weihanglo]

@bors r+ rollup=never p=1

[rust-bors]

📌 Commit 850787c has been approved by weihanglo

It is now in the queue for this repository.

[Kobzol]

@bors treeclosed=10 Linux x64 EC2 instances are not starting

@bors cancel

[rust-bors]

Tree closed for PRs with priority less than 10.

[rust-bors]

Auto build was cancelled. Cancelled workflows:

• https://github.com/rust-lang/rust/actions/runs/33941125531

The next pull request likely to be tested is #162317.

[JonathanBrouwer]

@bors p=6 scheduling

[rust-bors]

☀️ Test successful - CI
Approved by: weihanglo
Duration: 3h 11m 24s
Pushing 546f07f 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 0f819a1 (parent) -> 546f07f (this PR)

Test differences

Show 2 test diffs

Stage 2

• profile_trim_paths::multiple_options: pass -> [missing] (J0)
• profile_trim_paths::profile_merge_works: pass -> [missing] (J0)

Job group index

• J0: aarch64-apple-2, aarch64-apple-macos-26-2, aarch64-gnu, x86_64-gnu-aux, x86_64-msvc-ext1

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard 546f07f6ee18fa92e586e659ef888bbf0f99e6e7 --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. x86_64-gnu-stable: 1h 37m -> 2h 31m (+55.7%)
2. x86_64-gnu-distcheck: 1h 33m -> 2h 14m (+44.2%)
3. i686-gnu-2: 1h 34m -> 56m 24s (-40.6%)
4. x86_64-gnu-llvm-21: 37m 9s -> 51m 4s (+37.5%)
5. dist-arm-linux-musl: 1h 50m -> 1h 11m (-35.9%)
6. x86_64-gnu-llvm-22-3: 1h 22m -> 1h 51m (+35.5%)
7. dist-powerpc64-linux-gnu: 1h 10m -> 1h 34m (+33.5%)
8. x86_64-gnu-llvm-21-1: 57m 48s -> 39m 18s (-32.0%)
9. dist-x86_64-solaris: 1h 22m -> 1h 48m (+31.3%)
10. x86_64-mingw-1: 3h 6m -> 2h 8m (-31.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 (546f07f): comparison URL.

Overall result: ✅ improvements - no action needed

@rustbot label: -perf-regression

Instruction count

Our most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.

	mean	range	count
Regressions ❌ (primary)	-	-	0
Regressions ❌ (secondary)	-	-	0
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-0.3%	[-0.4%, -0.2%]	7
All ❌✅ (primary)	-	-	0

Max RSS (memory usage)

Results (primary -5.9%, secondary 0.4%)

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

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

Cycles

Results (primary 9.8%)

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

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

Binary size

Results (primary -0.0%, secondary -0.1%)

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

	mean	range	count
Regressions ❌ (primary)	-	-	0
Regressions ❌ (secondary)	-	-	0
Improvements ✅ (primary)	-0.0%	[-0.1%, -0.0%]	15
Improvements ✅ (secondary)	-0.1%	[-0.1%, -0.0%]	5
All ❌✅ (primary)	-0.0%	[-0.1%, -0.0%]	15

Bootstrap: 484.591s -> 478.607s (-1.23%)
Artifact size: 403.38 MiB -> 403.33 MiB (-0.01%)