Todd Strader

I'll revise this once #3875 lands. Really wish GitHub allowed stacked PRs . . .

Ah, yup. So, `--trace` is not a verilation-time parameter, it is something that you need to pass to the verilated binary. From looking at `Makefile.verilator` I think you could `PLUSARGS...

Whoops. You're right. Well, we're both right. `--trace` is both a verilation time parameter: ``` verilator --help | grep "\ " --trace Enable waveform creation ``` and a run time...

@WernerFS in order to get trace data you'll need to enable it at compile time (as you've done above with `--trace`) and you'll also need to pass `--trace` to the...

Is it still desired to abandon `vpiInertialDelay` and move entirely to `vpiNoDelay`? I'm reading through the backstory here (#1484 , #1662 , #1014 , #768 , #2178 ) and it...

Gotcha, so can you elaborate on what the desired behavior is? `38.34 vpi_put_value()` says: ``` vpiInertialDelay All scheduled events on the object shall be removed before this event is scheduled....

So are you saying that: * `.value` should use `vpiInertialValue` and not go through `Scheduler._write_calls` * `setimmediatevalue` should use `vpiNoDelay` I'm not sure what the Icarus implications are here, but...

OK, so let's focus on this one first: > setimmediatevalue should use vpiNoDelay I'm thinking the way to do this is to add `GPI_NO_DELAY` to `gpi_set_action_t` and have `setimmediatevalue()` use...

> We need a way to handle the icarus callback that will occur with `vpiNoDelay`. I'm guessing this has something to do with why the `issue_768_*` tests are failing on...

OK, cool. Thanks for the explainer. I'm currently seeing this: ``` 0.00ns INFO cocotb.regression issue_768.test failed Traceback (most recent call last): File "/usr/scratch/local/devs/cocotb-stock/tests/test_cases/issue_768_a/issue_768.py", line 21, in test assert dut.stream_in_data.value ==...