Re: [Iverilog-devel] Regression suite coverage statistics

[Cary R. <cy...@ya...>]

--- On Fri, 8/1/08, Nick Gasson <ni...@ni...> wrote:

> 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?

If the -f flags are part of CFLAGS they should get propagated
to the iverilog-vpi script. You could look there and if they
are missing you could add them and see if that fixes the
problem. The compiler options are passed to iverilog-vpi, but
it ignores options it doesn't understand instead of passing
them untouched.

Cary