From: Peter Watkins <peter_watkins@mentor.com>
To: gcc-help@gcc.gnu.org
Subject: Reducing testcase sets using GCC
Date: Thu, 17 Feb 2011 17:17:00 -0000 [thread overview]
Message-ID: <4D5D5261.5070208@mentor.com> (raw)
Our company has a suite of testcases we run before checking in code.
We'd like to reduce the number of tescases we have to run by running
only the testcases affected by the source code changes the developer
made. We have code coverage data for each testcase in the form of
functions covered. i.e. each testcase knows which C++ functions in our
product get called when the testcase executes.
I'm trying to determine which functions got changed in our product based
on the changes a developer made to the source code. So given foo-new.cxx
and foo-old.cxx, I'd like to know which functions are different between
these two.
Presently I'm planning on comparing pre-processed copies of the two
version. i.e. diff foo-new.i foo-old.i. Then from the diff, I'll try to
determine which functions are changed. However I'm not familiar with
GCC's plethora of options and debug outputs.
Does GCC provide an easy way of telling if a function or symbol changed
between two versions of a source file? Has anyone else faced the problem
of reducing a set of testcases given a set of source code changes? How
did you solve the problem?
Thanks,
Peter
reply other threads:[~2011-02-17 16: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=4D5D5261.5070208@mentor.com \
--to=peter_watkins@mentor.com \
--cc=gcc-help@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).