`-Z split-dwarf-kind={single,split}` is undocumented in the unstable book
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
Implementation history:
- In rustc: Stabilize
-Z run-dsymutilas-C split-debuginfo#79570:-Z split-dwarf=singlebecame-C split-debuginfo=packed-Z split-dwarf=splitbecame-C split-debuginfo=unpacked
- However, as @davidtwco noted in 08ed338f561b000ce5672b55c0545fa7f3f13591 (cg: split dwarf for crate dependencies #89819):
In https://github.com/rust-lang/rust/pull/79570,
-Z split-dwarf-kind={none,single,split}was replaced by-C split-debuginfo={off,packed,unpacked}.-C split-debuginfo's packed and unpacked aren't exact parallels to single and split, respectively. - As such, #89819 introduced
-Z split-dwarf-kind={single,split}to fill in the gap.
This unstable compiler flag doesn't seem to have an entry in the unstable book, I only discovered them while looking at tests/run-make/split-debuginfo. It would be nice to document its behavior and also the meaning of its values.
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 unstable book and compare its existing compiler-flag entries with the behavior described in this issue. Read tests/run-make/split-debuginfo for the documented flag usage and verify the entry explains -Z split-dwarf-kind={single,split} and the meanings of both values.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100