Proposal

I would add riscv64-unknown-openbsd support to rustc as tier 3 target.

Tier 3 target policy

• must have a designated developer
  • I am already designated developer for OpenBSD and intent to take this one too
• must use naming consistent with any existing targets
  • riscv64-unknown-openbsd follows naming at OpenBSD and naming for LLVM triple
• must not create legal issues or impose onerous legal terms for the Rust project or for Rust developers or users
• neither this policy nor any decisions made regarding targets shall create any binding agreement or estoppel by any party
• should attempt to implement as much of the standard libraries as possible and appropriate
  • the implementation is as complete as others OpenBSD targets (std and host are natively compiled)
• must provide documentation for the Rust community explaining how to build for the target, using cross-compilation if possible
  • native compilation works out-of-box
• must not impose burden on the authors of pull requests, or other developers in the community, to maintain the target
• Patches adding or updating tier 3 targets must not break any existing tier 2 or tier 1 target, and must not knowingly break another tier 3 target without approval of either the compiler team or the maintainers of the other tier 3 target

Mentors or Reviewers

I am already designated developer for OpenBSD targets.

The implementation is already done and used in OpenBSD ports infrastructure.

Process

The main points of the Major Change Process are as follows:

• File an issue describing the proposal.
• A compiler team member or contributor who is knowledgeable in the area can second by writing @rustbot second.
  • Finding a "second" suffices for internal changes. If however, you are proposing a new public-facing feature, such as a -C flag, then full team check-off is required.
  • Compiler team members can initiate a check-off via @rfcbot fcp merge on either the MCP or the PR.
• Once an MCP is seconded, the Final Comment Period begins. If no objections are raised after 10 days, the MCP is considered approved.

You can read more about Major Change Proposals on forge.

Comments

This issue is not meant to be used for technical discussion. There is a Zulip stream for that. Use this issue to leave procedural comments, such as volunteering to review, indicating that you second the proposal (or third, etc), or raising a concern that you would like to be addressed.