[RegisterOptimization] Need fixpoint iteration?
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2.2k
- Forks
- 524
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 46
Description
Since RegisterOptimization processes each register only once, the pass cannot optimizes the following IR (which IMCP was able to optimize):
```mlir
// circt-opt -pass-pipeline='builtin.module(firrtl.circuit(firrtl.module(firrtl-register-optimizer)))'
firrtl.circuit "Top" {
firrtl.module @Top(in %a: !firrtl.uint<1>, in %clock: !firrtl.clock, out %b: !firrtl.uint<1>) {
%r1 = firrtl.reg %clock : !firrtl.clock, !firrtl.uint<1>
%r2 = firrtl.reg %clock : !firrtl.clock, !firrtl.uint<1>
firrtl.strictconnect %r1, %r2 : !firrtl.uint<1>
%c0_ui1 = firrtl.constant 0 : !firrtl.uint<1>
firrtl.strictconnect %r2, %c0_ui1 : !firrtl.uint<1>
firrtl.strictconnect %b, %r1 : !firrtl.uint<1>
}
}
```
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 reproducing the provided FIRRTL IR with the circt-opt pass pipeline and then read the RegisterOptimization pass implementation. The work is done when the pass can repeatedly process registers until the example reaches the same optimization result that IMCP produced.
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
- 35/100