From: "Martin Liška" <mliska@suse.cz>
To: Sebastian Huber <sebastian.huber@embedded-brains.de>,
gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] gcov-tool: Allow merging of empty profile lists
Date: Thu, 24 Mar 2022 11:29:10 +0100 [thread overview]
Message-ID: <930c7bec-aea5-9491-94cd-a4e8c86f9bfe@suse.cz> (raw)
In-Reply-To: <76777016-d1d4-6e44-59f6-fbe3ff8249ac@embedded-brains.de>
On 3/23/22 15:50, Sebastian Huber wrote:
> The attached script reads the log file and creates the *.gcda files using gcov-tool. Initially, the target files do not exist.
Now I've got your use-case and I like it. It's cool one can utilize GCOV even without a filesystem.
Please update the patch. I basically don't see any issues with it.
Cheers,
Martin
next prev parent reply other threads:[~2022-03-24 10:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 9:34 Sebastian Huber
2022-03-23 12:19 ` Martin Liška
2022-03-23 14:50 ` Sebastian Huber
2022-03-24 10:29 ` Martin Liška [this message]
2022-03-24 10:51 ` Sebastian Huber
2022-03-24 12:03 ` Martin Liška
2022-03-28 16:23 ` Sebastian Huber
2022-03-30 11:56 ` Martin Liška
2022-03-30 13:30 ` Sebastian Huber
2022-03-30 14:48 ` Sebastian Huber
2022-03-31 6:58 ` Martin Liška
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=930c7bec-aea5-9491-94cd-a4e8c86f9bfe@suse.cz \
--to=mliska@suse.cz \
--cc=gcc-patches@gcc.gnu.org \
--cc=sebastian.huber@embedded-brains.de \
/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).