You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
The text was updated successfully, but these errors were encountered:
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.
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:
Based on this, would you be open distributing it? If so, what remains to be done?
Thanks in advance!
The text was updated successfully, but these errors were encountered: