public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/94928] Doc comments in gcov-io.h do not show cwd and unexec blocks in the Notes file format
Date: Wed, 06 May 2020 14:21:02 +0000	[thread overview]
Message-ID: <bug-94928-4-CtVQqn5Wd5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94928-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94928

--- Comment #10 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to Myron Walker from comment #9)
> How you I process data files from multiple sources and multiple runs with
> gcov.

$ man gcov-tool

$ gcov-tool merge [merge-options] directory1 directory2

So you basically take 2 folders of 2 runs and merge them into a destination
one.
The folders are traversed for .gcda files and corresponding files are merged.
Having N runs, you need to run log2(N) merge operations.

  parent reply	other threads:[~2020-05-06 14:21 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-02 22:09 [Bug gcov-profile/94928] New: " myron.walker at gmail dot com
2020-05-04  5:38 ` [Bug gcov-profile/94928] " marxin at gcc dot gnu.org
2020-05-06  9:14 ` marxin at gcc dot gnu.org
2020-05-06 13:13 ` myron.walker at gmail dot com
2020-05-06 13:17 ` marxin at gcc dot gnu.org
2020-05-06 13:31 ` myron.walker at gmail dot com
2020-05-06 13:38 ` marxin at gcc dot gnu.org
2020-05-06 13:52 ` myron.walker at gmail dot com
2020-05-06 13:59 ` marxin at gcc dot gnu.org
2020-05-06 14:04 ` marxin at gcc dot gnu.org
2020-05-06 14:14 ` myron.walker at gmail dot com
2020-05-06 14:21 ` marxin at gcc dot gnu.org [this message]
2020-05-06 14:57 ` myron.walker at gmail dot com
2020-05-06 15:22 ` myron.walker at gmail dot com
2020-05-07  7:35 ` marxin at gcc dot gnu.org
2020-05-07 10:41 ` myron.walker at gmail dot com
2020-05-07 11:17 ` marxin at gcc dot gnu.org
2020-05-07 13:37 ` myron.walker at gmail dot com
2020-05-11  7:22 ` marxin at gcc dot gnu.org
2020-05-11  7:26 ` cvs-commit at gcc dot gnu.org
2020-05-11  8:06 ` marxin at gcc dot gnu.org
2020-05-11 14:45 ` myron.walker at gmail dot com
2020-05-11 18:36 ` marxin at gcc dot gnu.org
2020-05-11 19:05 ` myron.walker at gmail dot com
2020-05-13 13:38 ` marxin at gcc dot gnu.org

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=bug-94928-4-CtVQqn5Wd5@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).