From: Joel Sherrill <joel.sherrill@oarcorp.com>
To: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: gcno file question
Date: Thu, 24 Mar 2011 12:59:00 -0000 [thread overview]
Message-ID: <4D8B3ED6.4030401@oarcorp.com> (raw)
Hi,
RTEMS has been using simulators and some
programs we wrote for coverage analysis
for a while now.
I am looking into writing a converter which
takes coverage data from simulators and produces
.gcno files. The coverage data is often just
a bitmap of which addresses were executed. There
is no frequency, just yes/no. We can already
map that information back to file/line.
+ Is this enough to produce a .gcno file from?
+ What records need to be generated as a minimum?
As a technical sanity question, the RTEMS code
is in a library and we are merging coverage
data from multiple executables to get unified
coverage data. We abstract away physical
address into offsets into methods and file/line.
Does generating a .gcno from this merged data
sound feasible?
Thoughts, insights, comments appreciated.
Thanks.
--
Joel Sherrill, Ph.D. Director of Research& Development
joel.sherrill@OARcorp.com On-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35805
Support Available (256) 722-9985
reply other threads:[~2011-03-24 12:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4D8B3ED6.4030401@oarcorp.com \
--to=joel.sherrill@oarcorp.com \
--cc=gcc@gcc.gnu.org \
/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).