github-actions[bot] on nightly
synth/elab-vhdl_expr: handle sl… testsuite/synth: add a test for… (compare)
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.
Yes, but my point is that the warning I want to backtrace is at simulation time
I think that using the warn arguments for analysis and elaboration is not limited to those stages. You are telling GHDL that you want those features enabled.