raxrbx64
For starters, it doesn’t seem to scale well. For a moderately complex design, it takes on the order of several minutes to generate Verilog code. When trying to work in a tight iteration debug loop this very much hinders productivity. In addition, it tends to eat up memory, too.
This is more of a scala/sbt thing, but typically the Chisel verilog generator is run via sbt which seems to only be able to run one thing at a time, so generating multiple (independent) modules described in the same project is not parallelizable without some finagling.
One thing I’ve noticed is, in an effort to support stable flattening and unflattening bundles to bit-vectors, the Chisel frontend will spend a large amount of its time doing reflection to get (bundle) class member names and sorting them (This I found after running it through a profiler – I apologize I don’t have those results handy).
The standard config environment for Chisel, CDE, makes things hard to understand because configuration for a design isn’t all kept in one place, but might be partially modified at any point in the code. This negatively impacts readability because one has to dive through and essentially understand the run-time call-stack in order to properly assemble the configuration in their head to diagnose why a particular value is set a certain way. (Reminds me of CSS, actually).
Also, CDE is essentially a layered switch case statement, which means it has O(n) lookup time which is also a big perf hit. In addition, each layer that does not contain a value throws an exception which also impacts performance when a large number of config lookups are happening in a design.