Update cc-rs to 1.2.39

[dpaoliello]

For my purposes, contains fixes when compiling the Rust compiler for Arm64EC.

Checked the commits since 1.2.16, and I don't see anything else that may affect Rust?

find-msvc-tools was also factored out from cc to allow updating the use in rustc_codegen_ssa (finding the linker when running the Rust compiler) to be separate from the use in rustc_llvm (building LLVM as part of the Rust compiler).

[rustbot]

Failed to set assignee to NobodyXu: invalid assignee

Note: Only org members with at least the repository "read" role, users with write permissions, or people who have commented on the PR may be assigned.

[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.

Some changes occurred in compiler/rustc_codegen_ssa

cc @WaffleLapkin

[jieyouxu]

@bors try jobs=aarch64-msvc-1,aarch64-apple,test-various,dist-apple-various

[rust-bors]

☀️ Try build successful (CI)
Build commit: d8ac12e (d8ac12e3b0cef5271092800d62ab852417973355, parent: a1208bf765ba783ee4ebdc4c29ab0a0c215806ef)

[jieyouxu]

Let me know @dpaoliello if you want to try with find-msvc-tools, otherwise I'm fine with the current change as well.
@rustbot author

[rustbot]

Reminder, once the PR becomes ready for a review, use @rustbot ready.

[dpaoliello]

I switched to find-msvc-tools, since I was here changing things.

@rustbot ready

[rustbot]

The list of allowed third-party dependencies may have been modified! You must ensure that any new dependencies have compatible licenses before merging.

cc @davidtwco, @wesleywiser

[davidtwco]

@bors r=davidtwco,jieyouxu

[bors]

📌 Commit 45a0e10 has been approved by davidtwco,jieyouxu

It is now in the queue for this repository.

[rust-bors]

💔 Test for 9cd2e4c failed: CI. Failed jobs:

• try - test-various (web logs, extended logs)

[dpaoliello]

try failure looks like a docker timeout.

Retrying...
@bors2 try jobs=dist-aarch64-linux,aarch64-msvc-1,aarch64-apple,test-various,dist-apple-various

[rust-bors]

☀️ Try build successful (CI)
Build commit: c2755aa (c2755aadb42e9221ae8576d267a57d65307ee733, parent: ab925646fae038b02bd462cd328ae9eef1639236)

[dpaoliello]

@rustbot ready

[jieyouxu]

@dpaoliello could you squash the commits and fixup the commit message to say 1.2.39 instead of 1.2.33 (from the previous attempts)? Otherwise, this looks good to me.

[jieyouxu]

@rustbot author

[dpaoliello]

Done

@rustbot ready

[jieyouxu]

Thanks

View changes since this review

[jieyouxu]

@bors r+ rollup=never

[bors]

📌 Commit 826c925 has been approved by jieyouxu

It is now in the queue for this repository.

[bors]

⌛ Testing commit 826c925 with merge bc1d727...

[bors]

☀️ Test successful - checks-actions
Approved by: jieyouxu
Pushing bc1d727 to master...

[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 c9537a9 (parent) -> bc1d727 (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 bc1d7273dfbc6f8a11c0086fa35f6748a13e8d3c --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-loongarch64-musl: 10893.4s -> 5156.0s (-52.7%)
2. dist-loongarch64-linux: 11354.2s -> 5538.0s (-51.2%)
3. pr-check-1: 1890.9s -> 1300.6s (-31.2%)
4. aarch64-apple: 8224.5s -> 6892.9s (-16.2%)
5. armhf-gnu: 4783.2s -> 5547.6s (16.0%)
6. dist-apple-various: 3959.6s -> 4533.5s (14.5%)
7. x86_64-gnu-llvm-20-1: 3700.0s -> 3255.6s (-12.0%)
8. dist-i586-gnu-i586-i686-musl: 5332.8s -> 4750.4s (-10.9%)
9. dist-x86_64-apple: 6383.1s -> 7051.9s (10.5%)
10. x86_64-gnu-llvm-20-2: 5415.8s -> 5973.3s (10.3%)

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.