Protect against --protect-lib Verilator runtime incompatibility #1518
Comments
Original Redmine Comment 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. |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
The text was updated successfully, but these errors were encountered: