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

Closed
veripoolbot opened this issue Nov 23, 2018 · 2 comments
Closed

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

veripoolbot opened this issue Nov 23, 2018 · 2 comments
Labels
area: performance Issue involves performance issues resolution: abandoned Closed; not enough information or otherwise never finished

Comments

@veripoolbot
Copy link
Contributor


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
Copy link
Contributor Author


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

@veripoolbot veripoolbot added area: performance Issue involves performance issues status: asked reporter Bug is waiting for reporter to answer a question labels Dec 22, 2019
@wsnyder wsnyder added resolution: abandoned Closed; not enough information or otherwise never finished and removed status: asked reporter Bug is waiting for reporter to answer a question labels May 2, 2020
@wsnyder
Copy link
Member

wsnyder commented May 2, 2020

Need example to proceed.

@wsnyder wsnyder closed this as completed May 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: performance Issue involves performance issues resolution: abandoned Closed; not enough information or otherwise never finished
Projects
None yet
Development

No branches or pull requests

2 participants