Add a dist component for cg_gcc

[Kobzol]

try-job: dist-x86_64-linux

[Kobzol]

@bors try

[antoyo]

You seem to be making changes to the dylibs stuff, so don't hesitate to ask me to test that this still works for cross-compiling rustc if you need me to.

[rust-bors]

💔 Test for 07629c3 failed: CI. Failed jobs:

• try - dist-x86_64-linux (web logs, enhanced plaintext logs)

[Kobzol]

I don't think my changes should affect the multi-target libgccjit dylib building, but if you can try, that would be helpful, of course :)

@bors try

[rust-bors]

☀️ Try build successful (CI)
Build commit: 09e4f11 (09e4f11d243b60bb64549da0285de0c149f80c9c, parent: 1b4325211c3228dd10eea12e9b3f749f87363d95)

[antoyo]

I don't think my changes should affect the multi-target libgccjit dylib building, but if you can try, that would be helpful, of course :)

Ok. Please tell me when this is ready and I'll do the test locally.

[Kobzol]

It is ready now, just waiting for #150535 to be reviewed and merged.

[antoyo]

It is ready now, just waiting for #150535 to be reviewed and merged.

I made my test and everything still seems to work.

[bors]

☔ The latest upstream changes (presumably #150535) made this pull request unmergeable. Please resolve the merge conflicts.

[rust-bors]

☔ The latest upstream changes made this pull request unmergeable. Please resolve the merge conflicts.

[rustbot]

Some changes occurred in src/tools/opt-dist

cc @Kobzol

[rustbot]

r? @clubby789

rustbot has assigned @clubby789.
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

[Kobzol]

r? @jieyouxu

[jieyouxu]

Thanks, one nit

View changes since this review

[jieyouxu]

@rustbot author

[jieyouxu]

@bors r+ rollup=never

[rust-bors]

📌 Commit 04707f4 has been approved by jieyouxu

It is now in the queue for this repository.

[rust-bors]

☀️ Test successful - CI
Approved by: jieyouxu
Pushing 32fe406 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 bca37a2 (parent) -> 32fe406 (this PR)

Test differences

No test diffs found

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard 32fe406b5e71afbb0d8b95280e50e67d1549224c --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-x86_64-apple: 7484.6s -> 9111.1s (+21.7%)
2. aarch64-apple: 9577.3s -> 11441.2s (+19.5%)
3. dist-aarch64-apple: 7314.4s -> 6024.5s (-17.6%)
4. dist-aarch64-msvc: 6344.1s -> 5425.6s (-14.5%)
5. i686-gnu-1: 8773.0s -> 7647.4s (-12.8%)
6. x86_64-gnu-tools: 3733.7s -> 3271.9s (-12.4%)
7. i686-gnu-2: 6110.2s -> 5367.3s (-12.2%)
8. x86_64-gnu-stable: 8729.2s -> 7678.5s (-12.0%)
9. aarch64-gnu-llvm-20-2: 3047.0s -> 2697.1s (-11.5%)
10. x86_64-gnu-gcc: 3823.6s -> 3400.8s (-11.1%)

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

Overall result: ❌ regressions - 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.6%	[0.5%, 0.6%]	3
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-	-	0
All ❌✅ (primary)	-	-	0

Max RSS (memory usage)

Results (primary -1.0%, secondary 3.6%)

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

	mean	range	count
Regressions ❌ (primary)	2.3%	[2.3%, 2.3%]	1
Regressions ❌ (secondary)	3.6%	[3.6%, 3.6%]	1
Improvements ✅ (primary)	-2.7%	[-2.8%, -2.5%]	2
Improvements ✅ (secondary)	-	-	0
All ❌✅ (primary)	-1.0%	[-2.8%, 2.3%]	3

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: 475.924s -> 474.424s (-0.32%)
Artifact size: 390.87 MiB -> 390.80 MiB (-0.02%)