Reducing testcase sets using GCC
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: gcc-help@xxxxxxxxxxx
- Subject: Reducing testcase sets using GCC
- From: Peter Watkins <peter_watkins@xxxxxxxxxx>
- Date: Thu, 17 Feb 2011 08:52:49 -0800
- User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101208 Lightning/1.0b2 Thunderbird/3.1.7
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
[Index of Archives]
[Linux C Programming]
[Linux Kernel]
[eCos]
[Fedora Development]
[Fedora Announce]
[Autoconf]
[The DWARVES Debugging Tools]
[Yosemite Campsites]
[Yosemite News]
[Linux GCC]