rust-lang / rust-lang/rust

Tracking Issue for `-Z llvm-plugins`

Open
#127,577 0 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

-Zllvm-plugins A-LLVM C-tracking-issue S-tracking-design-concerns S-tracking-needs-documentation T-compiler
Dominant language
Rust
Stars
119k
Forks
16.1k
PR merge metrics
PR metrics pending

Description

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
Unresolved Questions

This option currently only works on targets that use an llvm dylib, which is just x86_64-unknown-linux-gnu. On other targets LLVM is linked statically, and symbols needed by plugins are not visible.

Implementation history

Originally implemented in https://github.com/rust-lang/rust/pull/86267.

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 the rustc-dev-guide documentation and stabilization guides linked in the issue, then review the completed implementation PR #86267 for context on -Z llvm-plugins. Done means the documentation task is completed and the stabilization work has an appropriate PR, while accounting for the unresolved target limitations described here.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
compilers, documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.