|test suite for gcc frontend parser? firstname.lastname@example.org (Rizwan Mian) (2003-08-23)|
|Re: test suite for gcc frontend parser? email@example.com (Lex Spoon) (2003-09-04)|
|Re: test suite for gcc frontend parser? firstname.lastname@example.org (Ira Baxter) (2003-09-04)|
|From:||Lex Spoon <email@example.com>|
|Date:||4 Sep 2003 01:06:15 -0400|
|Organization:||Georgia Institute of Technology|
|Posted-Date:||04 Sep 2003 01:06:14 EDT|
Rizwan Mian <firstname.lastname@example.org> writes:
> I am writing some perl scripts to instrument C++ control flow
> constructs (e.g. functions, if-then-elses etc.) to dump out code
> coverage information.
A few quick comments.
First, why are you fixed on Perl? If you do it in C, or in any other
language that already has a C parser, you will save yourself some
hassle. Even if the rest of your project is in Perl, it should make
little difference, because this tool is likely to stand alone.
Also, by the way, gcc has a compilation option that will compile
programs with "profiling". This would give you some amount of
coverage information. Definitely check whether this is enough for
your purposes, before going further.
Finally, there are projects floating around on the net to do
instrumentation. Be sure to google a little before you invest your
own time making a new one. If you can't find anything out there and
decide to do it yourself, you should put it in on SourceForge. People
are interested in this sort of thing for various reasons, and you'll
probably get some synergy with them.
Return to the
Search the comp.compilers archives again.