Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Large increase in design header file with threads and tracing #1366

Open
veripoolbot opened this issue Nov 23, 2018 · 1 comment
Open

Large increase in design header file with threads and tracing #1366

veripoolbot opened this issue Nov 23, 2018 · 1 comment

Comments

@veripoolbot
Copy link

@veripoolbot veripoolbot commented Nov 23, 2018


Author Name: Al Grant
Original Redmine Issue: 1366 from https://www.veripool.org


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?

@veripoolbot

This comment has been minimized.

Copy link
Author

@veripoolbot veripoolbot commented Nov 29, 2018


Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2018-11-29T23:13:40Z


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)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.