[FIRRTL] ref.cast canonicalization patterns
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2.2k
- Forks
- 524
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 46
Description
* Simplify `ref.send -> ref.cast -> ref.resolve` (thanks: https://github.com/llvm/circt/pull/4825#discussion_r1204694929 )
* Fold ref.cast chains: `ref.cast(ref.cast(X, T1), T2) -> ref.cast(X, T2)`
Filing so don't forget but only makes sense if/once support for ref.cast op lands (#5323).
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 reading the ref.cast support tracked in issue #5323, then examine the FIRRTL canonicalization entry points for ref.send, ref.resolve, and ref.cast. Done means implementing the two listed simplifications: the ref.send-to-ref.resolve pattern and collapsing nested ref.cast operations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100