Emulation options should be consistent with each other
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 259
- Forks
- 84
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 72
Description
Currently, we do not do consistency checks for the passed emulation options. For example, -m <emulation> option simply overrides the other emulation options such as -mcpu <cpu> and -march <arch>. We should error-out if emulation options are inconsistent with each other, for example: ld.eld -o a.out /dev/null -m v68 -mcpu hexagonv99.
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 at the ld.eld command-line handling for -m, -mcpu, and -march, then trace how the selected emulation is applied. Done means inconsistent combinations such as -m v68 -mcpu hexagonv99 produce an error instead of one option silently overriding another; the payload names no files or tests to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- compilers, embedded-iot
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100