Kaleb Barrett
Kaleb Barrett
@imphil It's good to go. The only failing test is the Windows nox issue. If no one has anymore comments I'll merge.
Siemens has agreed to allow the illegal behavior in Questa 2022.1, so the Questa VHPI should fully support cocotb at that time, *without* changing the `ReadOnly` callback.
We are willing to accept any recommendations or changes to better support SVA's. There was another user interested in it (#2043). I have no idea what the requirements are, or...
xref #2018. To expand, we can't use `__del__` and `Py_Finalize` for this behavior as the cleanup order is not deterministic. Calling `gpi_sim_end` if initialization fails is appropriate, need to investigate...
#1217 is related.
To expand on the original inquiry about calling SystemVerilog tasks (or VHDL procedures) from cocotb the best to accomplish that is using the SystemVerilog-DPI for Verilog, or VHPIDIRECT in GHDL...
@eric-wieser Yeah, started looking more into it, it is a problem. We need something that behaves like a trigger so we can allow the simulator to advance and re-enter the...
From the little I know about it, DPI is just an FFI, it doesn't define any control. You can write testbench HDL code that calls into an imported C function,...
@eric-wieser I've been reading over the spec [1] and it seems that any caller can call any exported task given they first change their context to the scope where the...
There is also an Annex H (starting on page 1222) that gives more detail on the DPI. > The behavior of DPI utility functions that manipulate context is undefined when...