Feedthrough path detection
Nobody has claimed this yet.
- Dominant language
- SystemVerilog
- Stars
- 2.1k
- Forks
- 810
- Avg merge
- 5d 23h
- Merged PRs (30d)
- 9
Description
It may be worth having a CI check that looks for any feedthrough paths. We probably want some but only ones we've explicitly allowed.
We could use yosys to do this, waivers might be a little tricky, you could just name the start and end points but you may have multiple paths between those points and want to allow some but not others.
I will do some experimentation with yosys to see if I can come up with a workable solution.
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 proposed yosys experiment to determine whether feedthrough paths can be detected reliably in Ibex's CI flow. Investigate how waivers would identify allowed start and end points, including cases with multiple paths; done means there is a workable check and a defined way to allow only intended paths.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100