[firtool] OM MemorySchema prevents round-tripping FIRRTL output
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2.2k
- Forks
- 524
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 46
Description
When running a design through firtool with --repl-seq-mem enabled and --ir-fir to emit FIRRTL dialect IR, the resulting file cannot be run through firtool again to get SV output. The intermediate FIRRTL dialect IR file contains om.class @MemorySchema objects, which get re-created in the second run through firtool, which causes the verifier to detect a duplicate definition of @MemorySchema.
Should the --repl-seq-mem option be sensitive to classes already having been declared, and just update them if present?
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
Reproduce the two-stage firtool flow using --repl-seq-mem and --ir-fir, then inspect the emitted FIRRTL dialect IR for the om.class @MemorySchema definitions. Trace how the second invocation handles those existing classes; done means the round trip reaches SV output without a duplicate-definition verifier error.
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