Tracking Issue for bpf_target_feature
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
This is a tracking issue for bpf_target_feature, guarding target features on bpf.
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with compiler/rustc_target/src/target_features.rs to review the target features covered by bpf_target_feature, then read the linked discussion in issue #44839. The issue is complete only after ABI concerns are resolved, excluded features have separate gates, the Final Comment Period finishes, and a stabilization PR is merged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100