nvptx64 target - Moving towards lld
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.2k
- PR merge metrics
- PR metrics pending
Description
To move some RustWeek/dm discussions into an issue. In https://github.com/rust-lang/rust/pull/147672#issuecomment-4430021058, we were wondering if we could get rid of the NVIDIA-specific linker behaviour, since it would allow us to clean up code in multiple locations. It's also generally nicer and easier to test if we have the same setup.
Some requirements we are currently aware of, and which need to be verified when unsing lld:
We used to generate unsupported debug symbols.Fixed- Emitting PTX
- Handling libdevice
- Handling Linker::export_symbol
- (?)
cc @kjetilkjeka, @Flakebi, @kulst
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
No source files or tests are named. Start by tracing the nvptx64 target's NVIDIA-specific linker behavior and the existing lld path, using the linked pull request discussion for context. Verify that lld emits PTX, handles libdevice and Linker::export_symbol correctly, and does not reproduce the previously unsupported debug-symbol output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100