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

Moving aarch64-unknown-netbsd to Tier 2 #84475

Open
alarixnia opened this issue Apr 23, 2021 · 2 comments
Open

Moving aarch64-unknown-netbsd to Tier 2 #84475

alarixnia opened this issue Apr 23, 2021 · 2 comments
Labels
C-feature-request Category: A feature request, i.e: not implemented / a PR.

Comments

@alarixnia
Copy link
Contributor

AArch64 NetBSD (Tier 3) is fast approaching x86_64 NetBSD (Tier 2) in popularity among NetBSD users.

Is there any way we (speaking on behalf of the NetBSD project) can help in moving it to Tier 2? It may be possible to provide access to an AArch64 server for automated builds and testing, for example.

@jyn514
Copy link
Member

jyn514 commented Apr 23, 2021

@Niacat Our target policy is (finally) about to be documented in the RFCs repo: rust-lang/rfcs#2803. From skimming it I think the next step since it's already at tier 3 is to open an MCP in the compiler-team repo: https://github.com/rust-lang/compiler-team/issues/new/choose.

@yaahc
Copy link
Member

yaahc commented Feb 24, 2022

Hey @alarixnia, I'm taking a look1 into the target tier policy from the perspective of the library team because of a netbsd PR and am interested in getting netbsd's platform support2 documented. Looking at your comments in rust-lang/rfcs#2803 it seems like you were going to do this a while back but ran into difficulties with the process. Are you still interested in getting aarch64 netbsd moved to tier 2 and if so, can I help?

Footnotes

  1. https://github.com/rust-lang/libs-team/issues/39

  2. https://doc.rust-lang.org/nightly/rustc/platform-support.html

@Dylan-DPC Dylan-DPC added the C-feature-request Category: A feature request, i.e: not implemented / a PR. label Feb 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-feature-request Category: A feature request, i.e: not implemented / a PR.
Projects
None yet
Development

No branches or pull requests

4 participants