rust-lang / rust-lang/rust

Tracking Issue for hexagon_target_feature

Open
#150,250 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

A-target-feature C-tracking-issue T-compiler
Dominant language
Rust
Stars
119k
Forks
16.1k
PR merge metrics
PR metrics pending

Description

This is a tracking issue for hexagon_target_feature, guarding target features on hexagon.
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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. 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 guarded by hexagon_target_feature. Then read the linked stabilization guide and the checklist for ABI interactions, feature-gate separation, FCP, and stabilization. Done means the listed blockers are resolved and the tracking issue’s stabilization steps are completed.

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
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.