Skip to content

Distribute GCC backend #3756

Closed as not planned
Closed as not planned

Description

@GuillaumeGomez

Hi. Since rust-lang/rust#122334 was merged, I think it's now ready to start distributing the GCC backend through rustup. There are still limitations though:

  • For now we only build it for x86_64 linux target.
  • The backend is still very experimental and incomplete.

Based on this, would you be open distributing it? If so, what remains to be done?

Thanks in advance!

Activity

  1. rami3l commented on Apr 5, 2024

    @rami3l
    Member

    @GuillaumeGomez Hi, and thanks a lot for all the work!

    I'm very excited to see yet another codegen backend becoming available to end users!

    Looking at how rustc-codegen-cranelift got shipped in rust-lang/rust#81746, it looks like distributing a new component with Rustup is more about ensuring that the right manifests and artifacts are on the release server, and probably has little to do with the Rustup codebase (except for a few things like the rustup doc command where Rustup itself is responsible for consuming the component).

    I think you can start the experiment as long as you're sure that your component has a -preview suffix and is exclusively available on nightly, which is enough to show that it's still experimental. Again, just follow rust-lang/rust#81746.

    Currently I'm not aware of any special handling regarding codegen backends on Rustup's side, and given that this time some other party like Cargo is responsible for consuming this new component, I guess there's nothing to be changed from Rustup, but we'll have to wait and see. I'll keep this issue open just in case.

  2. added
    not-rustupWhatever is described in this issue isn't Rustup's fault
    on Jul 10, 2024
  3. rami3l commented on Sep 3, 2026

    @rami3l
    Member

    @GuillaumeGomez I hope everything has been going fine WRT the distribution of the GCC backend since then!

    I think now would be a good time to close this issue as stale, but if you have more concerns please feel free to let me know so we can reopen this or discuss this in another issue :]

  4. GuillaumeGomez commented on Sep 3, 2026

    @GuillaumeGomez
    MemberAuthor

    Didn't hear anything about it, so I guess it's fine? =D

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    not-rustupWhatever is described in this issue isn't Rustup's fault

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions