Adding `wasm32-unknown-unknown` to a Rust toolchain compiled against a specific LLVM revision
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
@Kobzol Chromium builds its Rust toolchain against a specific LLVM revision. I'm adding the wasm32-unknown-unknown target to that toolchain, so I need rust-lld to be available. It was working correctly until this PR, but now the stage1 compiler no longer generates rust-lld. I'm uncertain whether just copying lld as rust-lld would work across all platforms — I suspect there may be compatibility issues. Curious about your thoughts.
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 by reviewing the linked PR and the stage1 toolchain behavior that stopped generating rust-lld. Investigate whether the wasm32-unknown-unknown target can reliably obtain rust-lld across supported platforms; done means the target is available with a working linker in the specified-LLVM toolchain.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, wasm
- Domain
- build-system, compilers
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100