Krzysztof Bieganski
Krzysztof Bieganski
@wsnyder Not exactly, this PR is for JSON dumps which is our original goal. What got merged is the pre-PR that introduces `--json-only`. I suppose we can open a new...
Opened a new PR: https://github.com/verilator/verilator/pull/5020
This happens because Verilator unrolls the loop and inlines all the values, so instead of actually incrementing `i` and `j` it just directly uses constant values for the `$display`s, and...
That should actually work for this example. It probably errors out for you on some generate loops. I don't think there's a workaround for that, unfortunately.
> * `--quiet` - disable build time statistics printing Most people in the survey either want it as an opt-in, or don't want it/care about it. So maybe it'd be...
I looked into this, and prepared two patches for Verilator that fix your test case. However, they also break regression tests (at least the first one) so more work is...
Just noticed the `repeat` part of this is a duplicate of https://github.com/verilator/verilator/issues/4451
1. Like you said, the inlining is disabled with recursion, so it is related. From the perspective of the user impure recursive functions is the thing that doesn't work correctly....
Do the other causes of not-inlining break scheduling? If so, then I suppose the message should be more general. I admit I haven't looked into those, it's just this recent...
> Do we have models that break now because of this? e.g. does the UVM library itself as currently written have circular references that can cause leaks? Yes. UVM's `uvm_component`...