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

Protect against --protect-lib Verilator runtime incompatibility #1518

Open
veripoolbot opened this issue Sep 24, 2019 · 1 comment
Open

Protect against --protect-lib Verilator runtime incompatibility #1518

veripoolbot opened this issue Sep 24, 2019 · 1 comment

Comments

@veripoolbot
Copy link

@veripoolbot veripoolbot commented Sep 24, 2019


Author Name: Todd Strader (@toddstrader)
Original Redmine Issue: 1518 from https://www.veripool.org

Original Assignee: Todd Strader (@toddstrader)


Currently all --dpi-protect'ed modules and the top-level design share the same Verilator runtime symbols. Some options which have been suggested so far are:

  • Wrap the --dpi-protect'ed modules' runtimes in a unique namespace
  • Maintain a relatively stable and versioned Verilator API
@veripoolbot

This comment has been minimized.

Copy link
Author

@veripoolbot veripoolbot commented Sep 24, 2019


Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2019-09-24T12:16:08Z


Some items such as the mutexes for multithreading, tracing, VPI name lookup, and coverage are assumed to be common across all Verilated models. Perhaps some can be eliminated but probably not - for example there are only a certain number of physical CPUs so scheduling on more that that will tank performance. Some thought is needed on these.

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