Upgrade verilator
Open
Nobody has claimed this yet.
- Dominant language
- SystemVerilog
- Stars
- 2.1k
- Forks
- 810
- Avg merge
- 5d 23h
- Merged PRs (30d)
- 9
Description
In the future, it might be worth to upgrade Verilator to a more recent version. Especially when dealing with linting errors, a more recent version could get rid of some hacks to avoid certain linting errors (e.g., #2129).
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 issue #2129 and the linting setup to identify which Verilator version and linting hacks are involved. Done would require a defined target version and validation of the upgrade, but this issue does not specify files, tests, or a target version.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100