git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 1/8] Support coverage testing with GCC/gcov

From
Matthieu Moy <matthieu.moy@imag.fr>
Date
Feb 16, 2009, 09:39 UTC
Message-ID
<vpq3aeeoh53.fsf@bauges.imag.fr>
In-Reply-To
<fb1e427bf56f5061634bc57fe6837f75e36c6cb2.1234736374.git.trast@student.ethz.ch>
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 ...
> +COVERAGE_CFLAGS = $(CFLAGS) -O0 -ftest-coverage -fprofile-arcs
> +COVERAGE_LDFLAGS = $(CFLAGS)  -O0 -lgcov
... and this is not the one you are using anyway.
(but great thing to use gcov! thanks)
-- 
Matthieu
Previous: Thomas RastNext: Thomas Rast
Message 3 of 11 in “Support coverage testing with GCC/gcov”
  1. 0/8 Support coverage testing with GCC/gcovThomas Rast, Feb 15, 2009
  2. 1/8 Support coverage testing with GCC/gcovThomas Rast, Feb 15, 2009
  3. Matthieu MoyFeb 16, 2009
  4. Thomas RastFeb 16, 2009
  5. 2/8 Test that diff can read from stdinThomas Rast, Feb 15, 2009
  6. 3/8 Test diff --dirstat functionalityThomas Rast, Feb 15, 2009
  7. 4/8 Test log --graphThomas Rast, Feb 15, 2009
  8. 5/8 Test fsck a bit harderThomas Rast, Feb 15, 2009
  9. 6/8 Test log --decorateThomas Rast, Feb 15, 2009
  10. 7/8 Test rev-list --parents/--childrenThomas Rast, Feb 15, 2009
  11. 8/8 Test git-patch-idThomas Rast, Feb 15, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.