Add AscentLint lint target to Ibex
Nobody has claimed this yet.
- Dominant language
- SystemVerilog
- Stars
- 2.1k
- Forks
- 810
- Avg merge
- 5d 23h
- Merged PRs (30d)
- 9
Description
Currently we have a verible and a Verilator lint target in Ibex, and an AscentLint lint target in OpenTitan. Each target has an associated waiver file. For consistency, we should think about adding the AscentLint target to Ibex as well, together with the waiver file that currently lives at https://github.com/lowRISC/opentitan/blob/master/hw/ip/rv_core_ibex/lint/rv_core_ibex.waiver
We cannot run AscentLint in CI on Ibex, but we'll get the lint results by either manually running the tool (if someone has access to it), or as soon as Ibex is vendored into OT.
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
Compare Ibex’s existing Verible and Verilator lint targets with OpenTitan’s AscentLint setup. Start with hw/ip/rv_core_ibex/lint/rv_core_ibex.waiver in OpenTitan and determine where the corresponding Ibex waiver and target belong. Done means Ibex has an AscentLint target and associated waiver, with results obtainable manually or through future vendoring into OT.
Written by the indexing model from the issue text.
Assessment
- Domain
- embedded-iot, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100