Wilson Snyder
Wilson Snyder
P.S. Knowing if to calculate "mnemstr" and even trees of flops leading to such was the reason for the runtime traceEverOn, but that is not currently used.
Comnent applies to "not calculating" #6796, but also data table comment here. But that comment was beyond the original pull here. I have no objection to this pull.
I'm good with this, Geza indicated so earlier too, so merging.
Probably a mistake in where the error is determined in V3LinkDot, hopefully should be straight forward pull to make. I would suggest run with --debug, and look at the .tree...
@igorosky assuming @kbieganski doesn't have work sitting in a branch somewhere, any chance you might get to this after #6844? Trying to get closer to UVM... thanks
V3LinkDot only supports class and parameter types where this error happens. In later stages simply adding a ->skipRefp() would probably solve it, but it is likely more complicated here as...
Excellent!! Can you please make a github pull with that so we can review? There's many tutorials on that if you haven't done it before, e.g. https://www.google.com/search?q=how+to+make+a+github+fork+and+pull+request
Thanks for the good test case, I don't know how long edaplayground keeps examples so updated one below. I see what's going on, I will attempt a fix but is...
We are not supporting UVM yet (#1538). If you want to reduce this case to one showing the issue with e.g. sv-bugpoint (see [Reporting Verilator Bugs](https://verilator.org/guide/latest/contributing.html?highlight=test_regress#reporting-bugs) and section on use...
Thanks for reducing.