From: "Bernd Jendrissek" <bernd.jendrissek@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: gcov vs. multiple objects derived from the same source
Date: Wed, 05 Mar 2008 09:08:00 -0000 [thread overview]
Message-ID: <b39469680803050108m3355f7fak51ea46d11bdda202@mail.gmail.com> (raw)
[Please keep me Cc'ed as I am not subscribed.]
At work I have a bunch of source files that want to be compiled with
different CPPFLAGS. Since we now use automake, this implies that if
foo.c gets compiled into ${bindir}/bar, we get a file bar-foo.o, and
the same for the siblings of bar.
I'm worried that when I do gcov *.o, gcov might not notice that two
objects are derived from the same file, and thus the coverage notes
might reflect coverage only of a subset of the use cases - those that
exercise foo.c through ${bindir}/bar but not those that exercise it
through ${bindir}/baz.
Are there any guarantees (or specific lack thereof) about gcov's
behaviour under these circumstances?
next reply other threads:[~2008-03-05 9:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-05 9:08 Bernd Jendrissek [this message]
2008-03-07 1:15 ` Holger Blasum
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=b39469680803050108m3355f7fak51ea46d11bdda202@mail.gmail.com \
--to=bernd.jendrissek@gmail.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).