Add riscv32im-unknown-none-elf built-in target triple.

[ridwanabdillahi]

• Add built-in target riscv32im-unknown-none-elf.
• Update platform-support.md to list it as a Tier 3 target.

Below are details on how this target meets the requirements for tier 3:

A tier 3 target must have a designated developer or developers (the "target maintainers") on record to be CCed when issues arise regarding the target. (The mechanism to track and CC such developers may evolve over time.)

I would be willing to be a target maintainer, though I would appreciate if others with more experience around RISC-V volunteered to help with that as well.

Targets must use naming consistent with any existing targets; for instance, a target for the same CPU or OS as an existing Rust target should use the same name for that CPU or OS. Targets should normally use the same names and naming conventions as used elsewhere in the broader ecosystem beyond Rust (such as in other toolchains), unless they have a very good reason to diverge. Changing the name of a target can be highly disruptive, especially once the target reaches a higher tier, so getting the name right is important even for a tier 3 target.

Uses the same naming as the LLVM target, and the same convention as many other bare-metal targets.

Target names should not introduce undue confusion or ambiguity unless absolutely necessary to maintain ecosystem compatibility. For example, if the name of the target makes people extremely likely to form incorrect beliefs about what it targets, the name should be changed or augmented to disambiguate it.

I don't believe there is any ambiguity here.

Tier 3 targets may have unusual requirements to build or use, but must not create legal issues or impose onerous legal terms for the Rust project or for Rust developers or users.

I don't see any legal issues here.

The target must not introduce license incompatibilities.
Anything added to the Rust repository must be under the standard Rust license (MIT OR Apache-2.0).
The target must not cause the Rust tools or libraries built for any other host (even when supporting cross-compilation to the target) to depend on any new dependency less permissive than the Rust licensing policy. This applies whether the dependency is a Rust crate that would require adding new license exceptions (as specified by the tidy tool in the rust-lang/rust repository), or whether the dependency is a native library or binary. In other words, the introduction of the target must not cause a user installing or running a version of Rust or the Rust tools to be subject to any new license requirements.
If the target supports building host tools (such as rustc or cargo), those host tools must not depend on proprietary (non-FOSS) libraries, other than ordinary runtime libraries supplied by the platform and commonly used by other binaries built for the target. For instance, rustc built for the target may depend on a common proprietary C runtime library or console output library, but must not depend on a proprietary code generation library or code optimization library. Rust's license permits such combinations, but the Rust project has no interest in maintaining such combinations within the scope of Rust itself, even at tier 3.
Targets should not require proprietary (non-FOSS) components to link a functional binary or library.
"onerous" here is an intentionally subjective term. At a minimum, "onerous" legal/licensing terms include but are not limited to: non-disclosure requirements, non-compete requirements, contributor license agreements (CLAs) or equivalent, "non-commercial"/"research-only"/etc terms, requirements conditional on the employer or employment of any particular Rust developers, revocable terms, any requirements that create liability for the Rust project or its developers or users, or any requirements that adversely affect the livelihood or prospects of the Rust project or its developers or users.

I see no issues with any of the above.

Neither this policy nor any decisions made regarding targets shall create any binding agreement or estoppel by any party. If any member of an approving Rust team serves as one of the maintainers of a target, or has any legal or employment requirement (explicit or implicit) that might affect their decisions regarding a target, they must recuse themselves from any approval decisions regarding the target's tier status, though they may otherwise participate in discussions.
This requirement does not prevent part or all of this policy from being cited in an explicit contract or work agreement (e.g. to implement or maintain support for a target). This requirement exists to ensure that a developer or team responsible for reviewing and approving a target does not face any legal threats or obligations that would prevent them from freely exercising their judgment in such approval, even if such judgment involves subjective matters or goes beyond the letter of these requirements.

Only relevant to those making approval decisions.

Tier 3 targets should attempt to implement as much of the standard libraries as possible and appropriate (core for most targets, alloc for targets that can support dynamic memory allocation, std for targets with an operating system or equivalent layer of system-provided functionality), but may leave some code unimplemented (either unavailable or stubbed out as appropriate), whether because the target makes it impossible to implement or challenging to implement. The authors of pull requests are not obligated to avoid calling any portions of the standard library on the basis of a tier 3 target not implementing those portions.

core and alloc can be used. std cannot be used as this is a bare-metal target.

The target must provide documentation for the Rust community explaining how to build for the target, using cross-compilation if possible. If the target supports running tests (even if they do not pass), the documentation must explain how to run tests for the target, using emulation if possible or dedicated hardware if necessary.

Use --target=x86_64-unknown-none-elf option to cross compile, just like any target. The target does not support running tests.

Tier 3 targets must not impose burden on the authors of pull requests, or other developers in the community, to maintain the target. In particular, do not post comments (automated or manual) on a PR that derail or suggest a block on the PR based on a tier 3 target. Do not send automated messages or notifications (via any medium, including via @) to a PR author or others involved with a PR regarding a tier 3 target, unless they have opted into such messages.
Backlinks such as those generated by the issue/PR tracker when linking to an issue or PR are not considered a violation of this policy, within reason. However, such messages (even on a separate repository) must not generate notifications to anyone involved with a PR who has not requested such notifications.

I don't foresee this being a problem.

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.
In particular, this may come up when working on closely related targets, such as variations of the same architecture with different features. Avoid introducing unconditional uses of features that another variation of the target may not have; use conditional compilation or runtime detection, as appropriate, to let each target run code supported by that target.

No other targets should be affected by the pull request.

[rust-highfive]

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @matthewjasper (or someone else) soon.

Please see the contribution instructions for more information.

[rust-highfive]

⚠️ Warning ⚠️

• These commits modify compiler targets. (See the Target Tier Policy.)

[ridwanabdillahi]

Hello @matthewjasper would you happen to have a chance to look at this change? Or perhaps add in the relevant reviewers? Thanks!

@kraj I see you have added similar targets for riscv in the past, would you be able to look over this change as well? Thanks!

[kraj]

Hello @matthewjasper would you happen to have a chance to look at this change? Or perhaps add in the relevant reviewers? Thanks!

@kraj I see you have added similar targets for riscv in the past, would you be able to look over this change as well? Thanks!

sure

[ridwanabdillahi]

@estebank

I see you reviewed a similar PR, #82202, would you be able to look at this one as well?

[kraj]

lgtm

[wesleywiser]

r? @wesleywiser

[wesleywiser]

@bors r+

[Disasm]

but I believe a RISC-V working group already exists which maintain the other RISC-V builtin target triples with @Disasm being one of them.

I can't agree, I hear about this role for the first time :)

[ridwanabdillahi]

@Disasm

I can't agree, I hear about this role for the first time :)

I'm sorry, I may have added the wrong member. This file shows a risc-v team which I thought you were included in, https://github.com/rust-lang/team/blob/master/teams/risc-v.toml

[wesleywiser]

Just to clarify, there is a risc-v "notification group" which is used as a list of people who are familiar with a given topic and might be willing to answer questions about it or help with issues related to it. The risc-v notification group was created in rust-lang/team#362.

[kraj]

Just to clarify, there is a risc-v "notification group" which is used as a list of people who are familiar with a given topic and might be willing to answer questions about it or help with issues related to it. The risc-v notification group was created in rust-lang/team#362.

@wesleywiser Can you add me to this group as well? I do have interest in RISCV ports as I tinker with it often I can perhaps offer some help.

[ridwanabdillahi]

Just to clarify, there is a risc-v "notification group" which is used as a list of people who are familiar with a given topic and might be willing to answer questions about it or help with issues related to it.

Ahhh I see. Thank you for the clarification on that @wesleywiser

[wesleywiser]

@bors r+

[bors]

📌 Commit eae6835 has been approved by wesleywiser

[bors]

⌛ Testing commit eae6835 with merge 9b1ba030c4ea5ab134cad0dd883fefb0dc70af55...

[bors]

💥 Test timed out

[rust-log-analyzer]

A job failed! Check out the build log: (web) (plain)

Click to see the possible cause of the failure (guessed by this bot)

[wesleywiser]

@bors retry

[bors]

⌛ Testing commit eae6835 with merge bce19cf...

[bors]

☀️ Test successful - checks-actions
Approved by: wesleywiser
Pushing bce19cf to master...

[rust-timer]

Finished benchmarking commit (bce19cf): comparison url.

Summary: This benchmark run did not return any relevant results. 5 results were found to be statistically significant but too small to be relevant.

If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf.

@rustbot label: -perf-regression