Consider emitting `NOCROSSREFS` for vram classes to avoid those segments referencing each other
Open
Nobody has claimed this yet.
feature in consideration
- Dominant language
- Linker Script
- Stars
- 12
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Contributor guide
No contributing guide indexed for this repository
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 reading the linked GNU LD NOCROSSREFS documentation, then inspect the repository to find where VRAM classes are emitted. No file, test, or entry point is named in the issue; done would mean determining whether those generated segments should receive NOCROSSREFS and implementing or documenting that behavior with validation.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100