Re: [Iverilog-devel] Regression suite coverage statistics

[Nick G. <ni...@ni...>]

Cary R. wrote:
> Are you also running the vpi tests? They will exercise parts
> of vvp that nothing else will. Also do you know why the three
> header files (arith.h, bufif.h and npmos.h) are marked as 0%
> when the associated cc files are not.
>   

I've just run these now (in addition to the vvp_reg tests, results here: 
http://www.nickg.me.uk/~nick/vvp_vpi_cov/). However, the VPI tests did 
not complete successfully: while iverilog-vpi runs OK, the tests fail 
when executing vvp with this error:

Compiling vpi/hello_poke.c...
Making hello_poke.vpi from  hello_poke.o...
hello_poke:`./hello_poke.vpi' failed to open using dlopen() because:
    ./hello_poke.vpi: undefined symbol: __gcov_merge_add.
$hello_poke: This task not defined by any modules. I cannot compile it.
vsim: Program not runnable, 1 errors.

I'm guessing this is a problem with the flags which are/aren't used to 
compile the VPI module. -fprofile-arcs -ftest-coverage are used to build 
the compiler, and these pull in the __gcov_XXX symbols. I noticed 
there's a "compiler options" field in the vpi_regress.list file. Do any 
additional flags get passed to the compiler?

> Also do you know why the three
> header files (arith.h, bufif.h and npmos.h) are marked as 0%
> when the associated cc files are not.

I'm not really sure. The highlighted lines are the class definitions, 
and from a small sample (arith.h, delay.h) it seems to be classes that 
use the default destructor. In e.g. arith.h the classes that do have 
destructors don't have this unexecuted highlighting. So'd I'd guess it's 
indicating that the default destructor is not being called.


Nick