[sgasho]

related: #164057

Since #162309 removed the clang-linker-wrapper step, nothing reads device.bin
anymore, and its triple/arch are already in the bitcode.

So, as the first step, I removed steps generating and extracting device.bin, instead we're going to use the device bitcode.

As a next step, the host pass could take the linked device output(.ptx for NVPTX, .elf for AMDGPU) instead, which
would remove the second codegen. I'd like to do that in a separate PR.

I'll update rustc-dev-guide in a follow-up PR in their repo.

I verified that this change works by running offload sample code on UofT gpunode.

r? ZuseZ4

[ZuseZ4]

Iterating over all functions to get a target-cpu doesn't seem great, but should work for now and become unnecessary with the follow-up PR, so lgtm. Thanks!

@bors r+ rollup

[rust-bors]

📌 Commit 80d95cc has been approved by ZuseZ4

It is now in the queue for this repository.

[rust-log-analyzer]

The job test-aarch64-msvc-1 failed! Check out the build log: (web) (plain enhanced) (plain)

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

---- [run-make] tests\run-make\clear-error-blank-output stdout ----

error: rmake recipe failed to complete
status: exit code: 101
command: "C:\\a\\rust\\rust\\build\\aarch64-pc-windows-msvc\\test\\run-make\\clear-error-blank-output\\rmake.exe"
stdout: none
--- stderr -------------------------------

thread 'main' (4436) panicked at C:\a\rust\rust\tests\run-make\clear-error-blank-output\rmake.rs:11:64:
called `Result::unwrap()` on an `Err` value: Os { code: 232, kind: BrokenPipe, message: "The pipe is being closed." }
---
Currently active steps:
test::RunMake { test_compiler: Compiler { stage: 2, host: aarch64-pc-windows-msvc, forced_compiler: false }, target: aarch64-pc-windows-msvc } at src\bootstrap\src\core\build_steps\test.rs:2108
test::Compiletest { test_compiler: Compiler { stage: 2, host: aarch64-pc-windows-msvc, forced_compiler: false }, target: aarch64-pc-windows-msvc, mode: run-make, suite: "run-make", path: "tests/run-make", compare_mode: None } at src\bootstrap\src\core\build_steps\test.rs:2108
Build completed unsuccessfully in 1:59:49
make: *** [Makefile:115: ci-msvc-py] Error 1
  local time: Sat Oct 17 21:27:48 PDT 2026
  network time: Sun, 18 Oct 2026 04:27:48 GMT
##[error]Process completed with exit code 2.
##[group]Run echo "disk usage:"
echo "disk usage:"

[rust-bors]

💔 Test for 42d559d failed: CI. Failed job:

• auto - test-aarch64-msvc-1 (web logs, enhanced plaintext logs)

[ZuseZ4]

spurious

@bors r+ rollup

[rust-bors]

📌 Commit 80d95cc has been approved by ZuseZ4

It is now in the queue for this repository.

A failed build status on this PR was cleared due to the approval.

[rust-bors]

☀️ Test successful - CI
Approved by: ZuseZ4
Duration: 2h 51m 55s
Pushing 33295d7 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 02fb0a1 (parent) -> 33295d7 (this PR)

Test differences

Show 2 test diffs

2 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 33295d734447c7a2c22c44190f11bce6164a035a --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-i686-linux: 1h 11m -> 1h 57m (+63.4%)
2. dist-arm-linux-gnueabi: 1h -> 1h 36m (+59.6%)
3. dist-various-2: 33m 38s -> 51m 24s (+52.8%)
4. test-x86_64-rust-for-linux: 34m 32s -> 52m 29s (+52.0%)
5. dist-aarch64-apple: 1h 38m -> 2h 25m (+48.4%)
6. dist-powerpc64-linux-gnu: 1h 6m -> 1h 36m (+45.6%)
7. dist-ohos-x86_64: 56m 46s -> 1h 20m (+41.7%)
8. test-x86_64-msvc-ext1: 2h 11m -> 1h 19m (-39.7%)
9. test-i686-gnu-nopt-1: 1h 22m -> 1h 53m (+38.9%)
10. test-x86_64-gnu-debug: 2h 2m -> 1h 15m (-38.4%)

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 (33295d7): 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 (secondary -3.5%)

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
Improvements ✅ (secondary)	-3.5%	[-4.4%, -2.0%]	4
All ❌✅ (primary)	-	-	0

Cycles

Results (secondary 5.0%)

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)	5.0%	[5.0%, 5.0%]	1
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-	-	0
All ❌✅ (primary)	-	-	0

Binary size

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

Bootstrap: 489.75s -> 488.147s (-0.33%)
Artifact size: 409.00 MiB -> 408.98 MiB (-0.00%)