Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Protect against --protect-lib Verilator runtime incompatibility #1518
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:
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.