Coverage of backend rules

Coverage of backend rules

[Paulo J. Matos]

Hi,

I have a backend  and I would like to have a systematic way to know if
my testsuite covers all the define_insn and define_expand rules in my
md file.

What's the best way to achieve this?

I initially thought I could use gcov to check the coverage of the code
that is generated from the md file but I would like to know if there
is any better way to do this since I doubt I am the only one wishing
to do this.

Cheers,
-- 
PMatos

Re: Coverage of backend rules

[Ian Lance Taylor]

"Paulo J. Matos" <pocmatos@gmail.com> writes:


> I have a backend  and I would like to have a systematic way to know if
> my testsuite covers all the define_insn and define_expand rules in my
> md file.
>
> What's the best way to achieve this?

For define_insn you can use the -da option, and scan the debug files
for the matched insn names.  For define_expand you can reliably use
profiling information to look for calls to gen_NAME.

This approach won't tell you whether you are testing all alternatives
of all define_insns.  I don't know of a reasonable way to do that.

Ian

Re: Coverage of backend rules

[Paulo J. Matos]

On Tue, May 11, 2010 at 3:26 PM, Ian Lance Taylor <iant@google.com> wrote:

> For define_insn you can use the -da option, and scan the debug files
> for the matched insn names.  For define_expand you can reliably use
> profiling information to look for calls to gen_NAME.
>
> This approach won't tell you whether you are testing all alternatives
> of all define_insns.  I don't know of a reasonable way to do that.
>

Thanks for the tips. I will give it a go at trying to automate this.

Cheers,
-- 
PMatos