Some riscv-compliance tests are not passing at head on Verilator.
Open
Nobody has claimed this yet.
Component:RTL
IP:rv_core_ibex
Type:Icebox
- Dominant language
- SystemVerilog
- Stars
- 3.6k
- Forks
- 1.1k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 141
Description
`I-NOP-01` and `I-EBREAK-01` both time out after ten minutes, where the other tests don't take more than two. This should be investigated as a potential hardware bug. The easiest way to run the tests right now is via this soon-to-be-merged PR: https://github.com/lowRISC/opentitan/pull/11801
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 riscv-compliance tests I-NOP-01 and I-EBREAK-01, using the test-running approach in PR 11801. Reproduce the ten-minute timeouts on Verilator and compare them with the other compliance tests. Done means identifying the cause and determining whether it is a hardware bug, with the finding or corrective work documented.
Written by the indexing model from the issue text.
Assessment
- Domain
- embedded-iot, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100