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

RFC: Promote riscv64gc-unknown-linux-gnu to Tier-1 (without host tools) #3707

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

robin-randhawa-sifive
Copy link

@robin-randhawa-sifive robin-randhawa-sifive commented Oct 3, 2024

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


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.
Copy link
Member

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.

Copy link
Member

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.

@ehuss ehuss added T-compiler Relevant to the compiler team, which will review and decide on the RFC. T-infra Relevant to the infrastructure team, which will review and decide on the RFC. T-release Relevant to the release team, which will review and decide on the RFC. labels Oct 3, 2024
@programmerjake
Copy link
Member

I think there should be an explicit note in the tier list of targets that host tools are provided but they are tier 2.

@slanterns
Copy link
Contributor

@clarfonthey
Copy link
Contributor

clarfonthey commented Oct 4, 2024

I think there should be an explicit note in the tier list of targets that host tools are provided but they are tier 2.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T-compiler Relevant to the compiler team, which will review and decide on the RFC. T-infra Relevant to the infrastructure team, which will review and decide on the RFC. T-release Relevant to the release team, which will review and decide on the RFC.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants