From: Nathan Sidwell <nathan@codesourcery.com>
To: ransom@cs.pdx.edu
Cc: gcc@gcc.gnu.org, Janis Johnson <janis187@earthlink.net>
Subject: Re: [RFC] gcov tool, comparing coverage across platforms
Date: Mon, 27 Jun 2005 12:18:00 -0000 [thread overview]
Message-ID: <42BFEE96.7000206@codesourcery.com> (raw)
In-Reply-To: <1a2da76c1e1cee6a2486ac9ef61bd3c7@cs.pdx.edu>
ransom@cs.pdx.edu 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
nathan@codesourcery.com :: http://www.planetfall.pwp.blueyonder.co.uk
next prev parent reply other threads:[~2005-06-27 12:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-23 18:41 ransom
2005-06-27 12:18 ` Nathan Sidwell [this message]
2005-06-27 16:40 ` Joe Buck
2005-06-27 15:05 Dan Kegel
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=42BFEE96.7000206@codesourcery.com \
--to=nathan@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=janis187@earthlink.net \
--cc=ransom@cs.pdx.edu \
/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).