[FIRRTL] more strict connect semantic
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2.2k
- Forks
- 524
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 46
Description
I observe that, the current `firrtl.connect` only checks the src width not larger than the dst width, but not vice versa. since in the firrtl parser logic we already define some the padding and truncate logic, we can make firrtl.connect be more strict, e.g. checking width exactly same to find width bug in the early phase.
Contributor guide
No contributing guide indexed for this repository
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 locating the FIRRTL `firrtl.connect` implementation and reading the parser's existing padding and truncation logic. Determine where width compatibility is checked, then add coverage showing that mismatched source and destination widths are rejected while equal widths remain valid.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100