-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
RFC: Promote riscv64gc-unknown-linux-gnu to Tier-1 (without host tools) #3707
base: master
Are you sure you want to change the base?
Conversation
|
||
Not promoting the target could lead to a situation where the `riscv64gc-unknown-linux-gnu` tests are no longer passing, and this could impact users. | ||
|
||
Anecdotally, not having the Tier 1 'badge' has been seen to become an obstacle to increasing mindshare in Rust for this target. Organisations tend to associate a Tier 1 categorisation with better quality, suitability for key projects, longevity etc. With a reasonably justified Tier 1 'badge' in place, the likelihood is that such organisations will tend to pick up and promote the use of Rust in production. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should also discuss the option of having a vendor other than the rust-lang org provide the equivalent of Tier 1 support, e.g. by running CI externally and communicating equivalence properly.
That way even host tools could be tested without the infra burden of maintaining custom github runners.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That roughly happens with additional arches on Linux distros already.
I think there should be an explicit note in the tier list of targets that host tools are provided but they are tier 2. |
Better to link the previous Zulip discussion here: https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/Imminent.20RFC.20PR.3A.20riscv64gc-unknown-linux-gnu.20to.20Tier-1. |
Yeah, this greatly confused me until I saw this clarification. I was thinking that the host tools were being removed, but no, they're just not being promoted. Honestly, I think that maybe, it might be worth just separately classifying targets and host tools on entirely different lists at least when it comes to tiers, to avoid this kind of confusion, since it appears that they can truly be independently supported. Although I guess that it wouldn't ever make sense to have host tools at a higher tier than a target because, why would you allow building from something and not building for it? To clarify, I mean something along the lines of classifying ristv64gc-unknown-linux-gnu as "tier 1 target, tier 2 host tools," rather than "tier 1 without host tools." Or, perhaps just having two separate lists of supported targets and supported host tools. |
This RFC outlines the case for promoting the Rust riscv64gc-unknown-linux-gnu target to Tier-1 (without host tools) status.
Shout out to @Hoverbear, @danielsilverstone-ct for their support.
Rendered