From: Ian Lance Taylor <iant@google.com>
To: "Paulo J. Matos" <pocmatos@gmail.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Coverage of backend rules
Date: Tue, 11 May 2010 14:28:00 -0000 [thread overview]
Message-ID: <mcrr5lijyzk.fsf@dhcp-172-17-9-151.mtv.corp.google.com> (raw)
In-Reply-To: <AANLkTikC9sVtIKKu2FNee5-6duHNz7KuOQwp7kwbTCRJ@mail.gmail.com> (Paulo J. Matos's message of "Tue\, 11 May 2010 13\:35\:00 +0100")
"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
next prev parent reply other threads:[~2010-05-11 14:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-11 12:35 Paulo J. Matos
2010-05-11 14:28 ` Ian Lance Taylor [this message]
2010-05-12 16:39 ` Paulo J. Matos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=mcrr5lijyzk.fsf@dhcp-172-17-9-151.mtv.corp.google.com \
--to=iant@google.com \
--cc=gcc@gcc.gnu.org \
--cc=pocmatos@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).