Custom verilog emission
See original GitHub issueType of issue: other enhancement
What is the use case for changing the behavior?
@azidar mentioned that you were looking at adding a special node type to firrtl, @albertchen-sifive.
I’m interested in being able to support a use-case where a chisel annotation is used to emit custom verilog. For example, I’d like to be able to emit #ifdef guards for simulation around Analog
types so we can use Verilog real
.
Is this something close to what you’re working on? If so, I’d like to be involved.
Impact: unknown
Development Phase: proposal
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
SystemVerilog Event - ChipVerify
SystemVerilog Event. An event is a static object handle to synchronize between two or more concurrently active processes. One process will trigger the...
Read more >Support "Initial" based Reset in generated Verilog #938 - GitHub
FPGA Designs can use a Verilog initial block to reset their Registers and initial... ... This is custom verilog emission ...
Read more >freechipsproject/chisel3 - Gitter
I designed a circuit with chisel, and now I want to import the verilog file into Cadence to see the schematic. But cadence...
Read more >Frequently Asked Questions - Chisel/FIRRTL
I just want some Verilog; what do I do? I just want some FIRRTL; what do I do? Why doesn't Chisel tell me...
Read more >SystemVerilog output strategy (replacing/refactoring ...
I expect the general design to look similar to the custom op ... Refactor whatever is left of the old RTL/SV verilog emission...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think there are two things here. You’d like to be able to add transforms that run only for a specific emitter. You’d also like to be able to override how specific nodes are emitted and to add custom nodes where you define their emission behavior.
yep, I would like to add some custom node type that can be extended to emit things like #ifdef and such. I haven’t gotten around to implementing anything yet though. @azidar you mentioned that there was some cleanup on some of the firrtl passes that should be done before starting?