Wilson Snyder
Wilson Snyder
Closing - if make an example please reopen.
What matters is the variables those functions are called with, but yes, as the message says passing dynamic/queues is not currently supported. Please consider to make a pull to support...
The argument is ignored, see the documentation https://verilator.org/guide/latest/languages.html If you'd like to contribute a pull to fix this it would be welcome, otherwise we are unlikely to support this.
If you're not familiar with C programming this will probably be a frustrating project for you, so understand not doing it! It's something that is unsupported, if you feel better...
In most use cases people trace everything rather than specialize, so you are the first person to want this. There are lots of "easy" features that add up to years...
I don't understand why dumpvars can't be loaded before topp->trace is called at the top.
What the model uses to setup context information before the first eval is the __Syms constructor, e.g. this calls '__vm_contextp->timeunit'. That would be the place to pass the model's scopevars...
Thanks for these, BTW unless I see something that is in the wrong direction, I'll wait to review the pull as a whole when it comes.
Great, note that dumpvars doesn't take a string but takes multiple module and/or variable scopes. $dumpvars(3, top.foo.instname, top.foo.signame, top.foo.signame2);
Confirmed on others. Might you attempt a fix (presumably reorder statements in V3Fork)? Otherwise @kboronski-ant?