Rollup of 10 pull requests

[JonathanBrouwer]

Successful merges:

• Add optional CI job to build the compiler with the parallel frontend #153726 (Add optional CI job to build the compiler with the parallel frontend)
• Don't add empty target features for target-cpu=native on macOS #153763 (Don't add empty target features for target-cpu=native on macOS)
• Fix some comments about dataflow analysis. #153432 (Fix some comments about dataflow analysis.)
• Fix LegacyKeyValueFormat report from docker build: pr #153529 (Fix LegacyKeyValueFormat report from docker build: pr)
• fix(query): Pass Query Key to value_from_cycle_error #153694 (fix(query): Pass Query Key to value_from_cycle_error)
• unused_macro_rules switched used and unused comments #153717 (unused_macro_rules switched used and unused comments)
• add test that an incomplete feature emits a warning #153736 (add test that an incomplete feature emits a warning)
• editorconfig: css uses tabs #153748 (editorconfig: css uses tabs)
• rustc-dev-guide subtree update #153750 (rustc-dev-guide subtree update)
• actually make the is-fn test test what it says it tests #153762 (actually make the is-fn test test what it says it tests)

r? @ghost

Create a similar rollup

[JonathanBrouwer]

@bors r+ rollup=never p=5

[rust-bors]

📌 Commit cf8e79f has been approved by JonathanBrouwer

It is now in the queue for this repository.

[rust-bors]

☀️ Test successful - CI
Approved by: JonathanBrouwer
Duration: 3h 9m 41s
Pushing d097a0c 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 d1ee5e5 (parent) -> d097a0c (this PR)

Test differences

Show 13 test diffs

Stage 1

• [ui] tests/ui/feature-gates/incomplete-features.rs#expect: [missing] -> pass (J0)
• [ui] tests/ui/feature-gates/incomplete-features.rs#warn: [missing] -> pass (J0)
• [ui] tests/ui/parallel-rustc/fn-sig-cycle-ice-153391.rs: [missing] -> ignore (ignored always ((diagnostics flipflopping with Zthreads #142063))) (J0)

Stage 2

• [ui] tests/ui/feature-gates/incomplete-features.rs#expect: [missing] -> pass (J1)
• [ui] tests/ui/feature-gates/incomplete-features.rs#warn: [missing] -> pass (J1)
• [ui] tests/ui/parallel-rustc/fn-sig-cycle-ice-153391.rs: [missing] -> ignore (ignored always ((diagnostics flipflopping with Zthreads #142063))) (J1)

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

Job group index

• J0: x86_64-gnu-llvm-20-3, x86_64-gnu-llvm-21-3
• J1: aarch64-apple, aarch64-gnu, aarch64-gnu-llvm-20-1, aarch64-msvc-1, arm-android, armhf-gnu, dist-i586-gnu-i586-i686-musl, i686-gnu-1, i686-gnu-nopt-1, i686-msvc-1, test-various, x86_64-gnu, x86_64-gnu-debug, x86_64-gnu-gcc, x86_64-gnu-llvm-20, x86_64-gnu-llvm-20-2, x86_64-gnu-llvm-21-2, x86_64-gnu-nopt, x86_64-gnu-stable, x86_64-mingw-1, x86_64-msvc-1

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard d097a0cba9a42f8e37bd28d0d219e433938981ec --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. dist-aarch64-linux: 2h 24m -> 1h 55m (-20.3%)
2. dist-apple-various: 1h 41m -> 1h 59m (+17.0%)
3. x86_64-gnu-miri: 1h 34m -> 1h 20m (-15.0%)
4. x86_64-gnu-llvm-20: 1h 18m -> 1h 6m (-14.6%)
5. dist-aarch64-apple: 2h 22m -> 2h 3m (-13.2%)
6. x86_64-gnu-tools: 1h 3m -> 56m 2s (-11.9%)
7. i686-gnu-2: 1h 44m -> 1h 32m (-11.4%)
8. i686-gnu-1: 2h 23m -> 2h 7m (-11.2%)
9. pr-check-1: 31m 44s -> 28m 18s (-10.8%)
10. aarch64-msvc-1: 1h 59m -> 2h 12m (+10.8%)

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 (d097a0c): comparison URL.

Overall result: ❌✅ regressions and 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.3%	[0.3%, 0.3%]	1
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-0.0%	[-0.0%, -0.0%]	2
All ❌✅ (primary)	-	-	0

Max RSS (memory usage)

Results (primary -0.7%, secondary -0.9%)

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

	mean	range	count
Regressions ❌ (primary)	2.1%	[0.6%, 3.7%]	3
Regressions ❌ (secondary)	3.1%	[3.1%, 3.1%]	1
Improvements ✅ (primary)	-9.2%	[-9.2%, -9.2%]	1
Improvements ✅ (secondary)	-2.8%	[-4.7%, -1.0%]	2
All ❌✅ (primary)	-0.7%	[-9.2%, 3.7%]	4

Cycles

This benchmark run did not return any relevant results for this metric.

Binary size

This benchmark run did not return any relevant results for this metric.

Bootstrap: 480.488s -> 481.456s (0.20%)
Artifact size: 394.87 MiB -> 394.96 MiB (0.02%)