Tracking issue for MCP 994: Add `-Zllvm-target-feature` target *modifier* to directly set LLVM-level target features, and deprecate doing that with `-Ctarget-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 MCP "Add -Zllvm-target-feature target modifier to directly set LLVM-level target features, and deprecate doing that with -Ctarget-feature" (rust-lang/compiler-team#994).
[!NOTE]
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.
Instead, open a dedicated issue for the specific matter, link to this tracking issue and ping the MCP author.
Alternatively, post in the Zulip stream linked from the MCP.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
- Implement the MCP
- Initial implementation: https://github.com/rust-lang/rust/pull/160457
- Implement the special target modifier checks: https://github.com/rust-lang/rust/pull/160618
- Adjust the documentation
- In the Rust Compiler Development Guide if applicable (e.g., for refactorings)
- In the Rust Forge if applicable (e.g., for policy changes)
- In the rustc book if applicable (e.g., for target tier or CLI changes)
- In the Unstable Book if applicable (e.g., for unstable CLI changes)
Unresolved questions
None so far.
Implementation history
Empty so far.
@RalfJung, consider @rustbot claim'ing the work.
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 the tracking checklist and review the initial implementation in PR 160457, then inspect the remaining special target modifier checks in PR 160618. Check whether the Rust Compiler Development Guide, Rust Forge, rustc book, or Unstable Book needs documentation updates; done means the implementation checks and applicable documentation are complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100