Skip to content
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

Distribute GCC backend #3756

Open
GuillaumeGomez opened this issue Apr 5, 2024 · 1 comment
Open

Distribute GCC backend #3756

GuillaumeGomez opened this issue Apr 5, 2024 · 1 comment
Labels
not-rustup Whatever is described in this issue isn't Rustup's fault

Comments

@GuillaumeGomez
Copy link
Member

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!

@rami3l
Copy link
Member

rami3l commented Apr 5, 2024

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

@rami3l rami3l added the not-rustup Whatever is described in this issue isn't Rustup's fault label Jul 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
not-rustup Whatever is described in this issue isn't Rustup's fault
Projects
None yet
Development

No branches or pull requests

2 participants