From: "Martin Liška" <mliska@suse.cz>
To: "Jørgen Kvalsvik" <j@lambda.is>, gcc-patches@gcc.gnu.org
Cc: GCC Development <gcc@gcc.gnu.org>
Subject: Re: [PATCH] gcov: fix file and function summary information
Date: Wed, 24 Aug 2022 09:31:02 +0200 [thread overview]
Message-ID: <b7f25ebf-76c2-a112-81bf-aa256099d73c@suse.cz> (raw)
In-Reply-To: <cc089c7d-cc36-ec2d-7870-790c862b22a0@lambda.is>
On 8/24/22 09:12, Jørgen Kvalsvik wrote:
> I tested it and get the file summary as expected:
>
> File 'demo.cc'
> Lines executed:84.62% of 26
> Branches executed:100.00% of 6
> Taken at least once:50.00% of 6
> Calls executed:100.00% of 4
> Creating 'demo.cc.gcov'
>
> Thanks,
> Jørgen
Great, I've just pushed that as revision r13-2166-g42301c02e458cd.
Cheers,
Martin
prev parent reply other threads:[~2022-08-24 7:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 16:03 Should templates with multiple instantiations contribute to summaries in gcov? Jørgen Kvalsvik
2022-08-22 19:25 ` [PATCH] gcov: fix file and function summary information Martin Liška
2022-08-24 7:12 ` Jørgen Kvalsvik
2022-08-24 7:31 ` Martin Liška [this message]
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=b7f25ebf-76c2-a112-81bf-aa256099d73c@suse.cz \
--to=mliska@suse.cz \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=j@lambda.is \
/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).