Kaleb Barrett
Kaleb Barrett
Apparently there is a test to see if we can find a SV gate, but I'm not sure yet finding gates is even useful, so I'm testing to see if...
We can't see any signals under a gate object, so their discovery is not important. The `access_gate` test will be removed.
This is actually a bigger PITA than expected. Our "expected don't cares" are still passed back up to the GPI layer as NULLs, which get encoded as GPI_NOT_NATIVE objects, causing...
The discovery tests are now not finding certain objects. Investigation is needed to find out what's now missing after removing objects from iteration.
Rerunning CI.
Not sure we need to document `COCOTB_LIBRARY_COVERAGE` as it's for our regressions only.
We would definitely want to handle the immediate callback issue at the GPI implementation level (or even push the fix to the simulator if possible) and not in the Python...
Putting values in VHPI and FLI are *always* inertial, so `vpiInternalDelay` is more consistent *if* the effect is visible to the user. Ideally it should not be. If we are...
> I think the easiest way is to Force then immediately Release. This doesn't work. Even `Force`s are inertial. Is there anything analagous to `vpiNoDelay` in the VHPI @marlonjames?
After further investigation I'm leaning more towards not using `vpiNoDelay` and removing `setimmediatevalue` unless there is some path forward for consistent behavior. Currently `setimmediatevalue`'s only value is that because `_write_calls`...