Skip to content

Update GCC backend subtree #142669

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 66 commits into from
Jun 18, 2025

Conversation

GuillaumeGomez
Copy link
Member

No description provided.

GuillaumeGomez and others added 30 commits May 14, 2025 13:51
Add missing `add_eval` to generate `__rdl_oom` in the alloc error handler
make `rustc_attr_parsing` less dominant in the rustc crate graph

It has/had a glob re-export of `rustc_attr_data_structures`, which is a crate much lower in the graph, and a lot of crates were using it *just* (or *mostly*) for that re-export, while they can rely on `rustc_attr_data_structures` directly.

Previous graph:
![graph_1](https://github.com/user-attachments/assets/f4a5f13c-4222-4903-b56d-28c83511fcbd)

Graph with this PR:
![graph_2](https://github.com/user-attachments/assets/1e053d9c-75cc-402b-84df-86229c98277a)

The first commit keeps the re-export, and just changes the dependency if possible. The second commit is the "breaking change" which removes the re-export, and "explicitly" adds the `rustc_attr_data_structures` dependency where needed. It also switches over some src/tools/*.

The second commit is actually a lot more involved than I expected. Please let me know if it's a better idea to back it out and just keep the first commit.
Changes to constant handling - faster deduplication, more compact represtntation
Fix to 128 bit int unaligned loads
Add support for easily fuzzing `cg_gcc` with rustlantis
modifed y.sh to allow for running cargo tests.
Added some bare-bones support for explict registers in ARM inline assembly
Fix fuzz warnings and deny warnings by default in build system
@rustbot
Copy link
Collaborator

rustbot commented Jun 18, 2025

r? @WaffleLapkin

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

@rustbot rustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. labels Jun 18, 2025
@rustbot
Copy link
Collaborator

rustbot commented Jun 18, 2025

Some changes occurred in compiler/rustc_codegen_gcc

cc @antoyo, @GuillaumeGomez

@rustbot

This comment has been minimized.

@rustbot rustbot added has-merge-commits PR has merge commits, merge with caution. S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. labels Jun 18, 2025
Copy link
Contributor

@antoyo antoyo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for making this PR!

@GuillaumeGomez GuillaumeGomez force-pushed the subtree-update_cg_gcc_2025-06-18 branch from 693f386 to 9ead7af Compare June 18, 2025 13:08
@rustbot

This comment has been minimized.

@GuillaumeGomez GuillaumeGomez force-pushed the subtree-update_cg_gcc_2025-06-18 branch from 9ead7af to c48d8d4 Compare June 18, 2025 13:11
@rustbot
Copy link
Collaborator

rustbot commented Jun 18, 2025

⚠️ Warning ⚠️

@rust-log-analyzer

This comment has been minimized.

@GuillaumeGomez
Copy link
Member Author

@bors r+ rollup=never p=1

@bors
Copy link
Collaborator

bors commented Jun 18, 2025

📌 Commit 8648405 has been approved by GuillaumeGomez

It is now in the queue for this repository.

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. labels Jun 18, 2025
@bors
Copy link
Collaborator

bors commented Jun 18, 2025

⌛ Testing commit 8648405 with merge f9c15f4...

@bors
Copy link
Collaborator

bors commented Jun 18, 2025

☀️ Test successful - checks-actions
Approved by: GuillaumeGomez
Pushing f9c15f4 to master...

@bors bors added the merged-by-bors This PR was explicitly merged by bors. label Jun 18, 2025
@bors bors merged commit f9c15f4 into rust-lang:master Jun 18, 2025
11 checks passed
@rustbot rustbot added this to the 1.89.0 milestone Jun 18, 2025
@GuillaumeGomez GuillaumeGomez deleted the subtree-update_cg_gcc_2025-06-18 branch June 18, 2025 17:57
Copy link
Contributor

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 6f935a0 (parent) -> f9c15f4 (this PR)

Test differences

No test diffs found

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard f9c15f40fbd7b4ba1baea6fb89551274047e17b3 --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-apple-various: 5798.3s -> 9430.6s (62.6%)
  2. dist-aarch64-apple: 6158.2s -> 4853.1s (-21.2%)
  3. i686-gnu-2: 6187.3s -> 5396.2s (-12.8%)
  4. x86_64-rust-for-linux: 2905.0s -> 2543.3s (-12.4%)
  5. i686-gnu-nopt-1: 8177.2s -> 7184.2s (-12.1%)
  6. x86_64-gnu-llvm-19-1: 3688.3s -> 3292.8s (-10.7%)
  7. i686-gnu-1: 8234.2s -> 7374.2s (-10.4%)
  8. aarch64-apple: 5607.4s -> 5031.0s (-10.3%)
  9. x86_64-gnu-debug: 5925.5s -> 5329.2s (-10.1%)
  10. dist-aarch64-msvc: 8331.1s -> 9166.2s (10.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
Copy link
Collaborator

Finished benchmarking commit (f9c15f4): comparison URL.

Overall result: no relevant changes - no action needed

@rustbot label: -perf-regression

Instruction count

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

Max RSS (memory usage)

Results (secondary -0.8%)

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

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: 693.627s -> 694.089s (0.07%)
Artifact size: 371.96 MiB -> 372.00 MiB (0.01%)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
has-merge-commits PR has merge commits, merge with caution. merged-by-bors This PR was explicitly merged by bors. S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.