[EMAIL PROTECTED] wrote:
Current questions include whether this tool needs to be used on
platforms for which a bourne shell script is inappropriate and whether
this tool needs to be coded in C instead.
as you're somewhat deadline bound, write it in whatever language suits your
needs. bash would certainly be acceptable, but I wouldn't particularly mind if
it was in perl or python, which might be somewhat easier to work with.
Also, whether the -a, -b, -c
and -f output types from gcov all need to be accounted for or whether
only some of these outputs are of types for which cross-platform
comparison makes sense. We have little doubt that regular users of gcov
Seems a reasonable choice.
One other use of such a tool, that I suggested to Janis when she mentioned you
all, is to compare gcov results for the same target machine but at different
optimization levels. this might or might not change the block structure to a
greater extent.
nathan
--
Nathan Sidwell :: http://www.codesourcery.com :: CodeSourcery LLC
[EMAIL PROTECTED] :: http://www.planetfall.pwp.blueyonder.co.uk
