raise PrettyPrintException(pyGHDL.dom.formatting.prettyprint.PrettyPrintException: Unhandled constraint kind for signal 'rs2'.crash I was getting was because https://github.com/ghdl/ghdl/blob/master/pyGHDL/cli/DOM.py#L56. The prettyPrint call should be moved to L52-L53, so that it does not try to use it in case there was some exception.
std.envdoesn't exist in earlier versions of the standard.
-frelaxed, maybe newer GHDL versions allow using
std.envin older VHDL versions when that option is set
signal sig1, sig2, sig3 : bit;- will be handled soon).
Array_Subtype_Definition- will be handled soon.
Hey there !
I have a design which produce a lot of
../../src/ieee/v93/numeric_std-body.vhdl:1336:7:@0ms:(assertion warning): NUMERIC_STD."<=": metavalue detected, returning FALSE
While I know what produces it (uninitialized values), I would like to know which function produced it.
I wanted to trigger this warning as an error using
--warn-error and check the backtrace, but it seems that this option does'nt exists for simulation time (
-r command). Could you confirm this ?
As I run ghdl through cocotb, I don't have control over the actual command, I can only add parameters.
/opt/ghdl/bin/ghdl -r --workdir=sim_build -Psim_build --work=work ENTITY --vpi=/home/jfaucher/.local/lib/python3.8/site-packages/cocotb/libs/libcocotbvpi_ghdl.so --warn-error
SIM_ARGSsomewhere in your own Makefile: https://github.com/cocotb/cocotb/blob/master/cocotb/share/makefiles/simulators/Makefile.ghdl#L79
Makefile.ghdlinto your project.
COMPILE_ARGSwould be another candidate to try.
cocotb-config --lib-name-path vpi ghdl. And you will also need to set the
MODULEenvironment variable at a minimum to find tests. See my crappy basic Makefile I threw together because I didn't feel like figuring out which of the 3
*_ARGSvariables did the thing I needed it to.