Tracking Issue for riscv_target_feature

View all comments

This is a tracking issue for riscv_target_feature, guarding target features on riscv.
This is a catch-all issue for all target features on that target. See this file for a list of target features currently guarded by this feature gate.

See https://github.com/rust-lang/rust/issues/44839 for discussion from before this feature got its own tracking issue.

About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.
Discussion comments will get marked as off-topic or deleted.
Repeated discussions on the tracking issue may lead to the tracking issue getting locked.

Steps

• Figure out ABI interactions and other possible blockers/concerns
• Move target features that should not be part of the initial stabilization under separate feature gates
• Final Comment Period (FCP)
• Stabilization PR (see instructions on rustc-dev-guide)

Unresolved Questions

none at the moment

Implementation history

Start with compiler/rustc_target/src/target_features.rs to review the target features currently guarded by riscv_target_feature, then read the linked stabilization guide and the checklist in this tracking issue. The work is complete when ABI interactions and blockers are resolved, features needing separate gates are moved, and the final comment period and stabilization PR are finished.