From: Thomas Rast <trast@student.ethz.ch>
To: Matthieu Moy <Matthieu.Moy@imag.fr>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH 1/8] Support coverage testing with GCC/gcov
Date: Mon, 16 Feb 2009 12:09:28 +0100 [thread overview]
Message-ID: <200902161209.34188.trast@student.ethz.ch> (raw)
In-Reply-To: <vpq3aeeoh53.fsf@bauges.imag.fr>
[-- Attachment #1: Type: text/plain, Size: 784 bytes --]
Matthieu Moy wrote:
> detail:
>
> Thomas Rast <trast@student.ethz.ch> writes:
>
> > With gcc's --coverage option, we can perform automatic coverage data
>
> I don't think gcc has a --coverage ...
Mine does:
--coverage
This option is used to compile and link code instrumented for
coverage analysis. The option is a synonym for -fprofile-arcs
-ftest-coverage (when compiling) and -lgcov (when linking). See
the documentation for those options for more details.
> > +COVERAGE_CFLAGS = $(CFLAGS) -O0 -ftest-coverage -fprofile-arcs
> > +COVERAGE_LDFLAGS = $(CFLAGS) -O0 -lgcov
>
> ... and this is not the one you are using anyway.
Indeed, I guess the log message is somewhat misleading.
--
Thomas Rast
trast@{inf,student}.ethz.ch
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-02-16 11:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-15 22:25 [PATCH 0/8] Support coverage testing with GCC/gcov Thomas Rast
2009-02-15 22:25 ` [PATCH 1/8] " Thomas Rast
2009-02-16 9:39 ` Matthieu Moy
2009-02-16 11:09 ` Thomas Rast [this message]
2009-02-15 22:25 ` [PATCH 2/8] Test that diff can read from stdin Thomas Rast
2009-02-15 22:25 ` [PATCH 3/8] Test diff --dirstat functionality Thomas Rast
2009-02-15 22:25 ` [PATCH 4/8] Test log --graph Thomas Rast
2009-02-15 22:25 ` [PATCH 5/8] Test fsck a bit harder Thomas Rast
2009-02-15 22:25 ` [PATCH 6/8] Test log --decorate Thomas Rast
2009-02-15 22:25 ` [PATCH 7/8] Test rev-list --parents/--children Thomas Rast
2009-02-15 22:25 ` [PATCH 8/8] Test git-patch-id Thomas Rast
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=200902161209.34188.trast@student.ethz.ch \
--to=trast@student.ethz.ch \
--cc=Matthieu.Moy@imag.fr \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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 NNTP newsgroup(s).