Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
Large increase in design header file with threads and tracing #1366
Author Name: Al Grant
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?
Original Redmine Comment
Can you share an example of the sort of things that are getting massively expanded (e.g. are in the combined file but not when --trace standalone)?