On Tue, May 11, 2010 at 3:26 PM, Ian Lance Taylor 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
"Paulo J. Matos" 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
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
