lowRISC / lowRISC/opentitan

[otbn,dv] We don't hit extreme values of immediates in enc_i_cg

Open
#8,080 2 comments 0 reactions 0 assignees View on GitHub
Component:DV Earlgrey-PROD Candidate IP:otbn Milestone:V3 Priority:P2 Type:Enhancement
Dominant language
SystemVerilog
Stars
3.6k
Forks
1.1k
Avg merge
2d 22h
Merged PRs (30d)
141

Description

These instructions are generated by the StraightLineInsn generator. It may be enough to teach the code that picks immediate operands to favour the boundaries of the range. Grouped into this issue are a couple of other covergroups too:

- [ ] `enc_i_cg`
- [ ] `insn_addi_cg` (we don't add zero to anything)
- [ ] `enc_u_cg`

Contributor guide

Open the contributing guide

Research direction

Start by locating the StraightLineInsn generator and the covergroups named enc_i_cg, insn_addi_cg, and enc_u_cg. Check how immediate operands are selected and how coverage is measured. Done means the generated instructions hit immediate-range boundaries, insn_addi_cg covers adding zero, and all three covergroups are no longer missing coverage.

Written by the indexing model from the issue text.

Assessment

Domain
embedded-iot, testing
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.