Large increase in design header file with threads and tracing
When using both threads and tracing (VM_TRACE=1), and separate build steps for the design library (Vdesign__ALL.a) and C++ testbenches, a large increase is seen in the size of the generated design header file (Vdesign.h). For example a header that is 2Mb with either tracing or threads, becomes 10Mb with both. This makes testbenches significantly slower to recompile - especially in a situation where you are building the library once on some powerful machine and then importing it into testbenches on less powerful machines.
As it's up to Verilator how to split the design across threads, shouldn't there be only a small impact on the size of the external (testbench visible) interface?
Also available in: Atom