Kaleb Barrett
Kaleb Barrett
Thanks for the bump. Yeah I need to clean up old PRs at some point.
So since we have to support both FST and VCD outputs and that requires passing different arguments during build (ugh) we have documentation on how to do this specially with...
Also we should perhaps support top-level vs hierarchical parameters as separate options so any given options works the same.
We fixed this internally by prefixing the name of the param with the top module followed by a colon. i.e. `{top_module}:{name} => {value}`.
Yes. It is JUnit. But its also known to be invalid JUnit #4171. Help is appreciated.
I'll look at this later today.
@p12tic I think this PR can come in as is, but that does bring up a good point. We only ever support the most recently released version of cocotb, so...
@p12tic Sorry about the delay. We usually like to have more than one maintainer approve larger PRs or merge them after a couple days if there are no comments, but...
This should be fixed by #3391.
Not sure if putting these in separate classes is the best play. They become heap allocated, dynamically dispatched, and only 32-56 bytes smaller. Most of the overhead comes from `VerilatedVpioVar`...