From: "Jørgen Kvalsvik" <jorgen.kvalsvik@woven-planet.global>
To: gcc-patches@gcc.gnu.org
Cc: "Jørgen Kvalsvik" <jorgen.kvalsvik@woven-planet.global>
Subject: [PATCH 0/2] gcov: Split when edge locus differ from dest bb
Date: Wed, 5 Oct 2022 14:04:01 +0200 [thread overview]
Message-ID: <20221005120403.68935-1-jorgen.kvalsvik@woven-planet.global> (raw)
Original discussion: https://gcc.gnu.org/pipermail/gcc/2022-October/239544.html
Some tiny test additions as well as more accurate check for when to
split edges for coverage. This patch preserves the edge splitting
heuristic except using a slightly more precise comparison, but makes a
huge difference for the condition profiling [1].
I compared the .gcov files for the gcc and g++ testsuites with and
without this patch and found no differences, and bootstrapped on
x86_64-linux.
[1] https://gcc.gnu.org/pipermail/gcc-patches/2022-July/598165.html
Jørgen Kvalsvik (2):
gcov: test switch/break line counts
Split edge when edge locus and dest don't match
gcc/profile.cc | 18 +++++++++---------
gcc/testsuite/g++.dg/gcov/gcov-1.C | 8 ++++----
gcc/testsuite/gcc.misc-tests/gcov-4.c | 4 ++--
3 files changed, 15 insertions(+), 15 deletions(-)
--
2.30.2
next reply other threads:[~2022-10-05 12:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-05 12:04 Jørgen Kvalsvik [this message]
2022-10-05 12:04 ` [PATCH 1/2] gcov: test switch/break line counts Jørgen Kvalsvik
2022-10-05 12:27 ` Martin Liška
2022-10-05 12:04 ` [PATCH 2/2] Split edge when edge locus and dest don't match Jørgen Kvalsvik
2022-10-05 12:49 ` Martin Liška
2022-10-06 8:12 ` Richard Biener
2022-10-06 14:28 ` Jørgen Kvalsvik
2022-10-07 6:53 ` Richard Biener
2022-10-07 11:45 ` Jørgen Kvalsvik
2022-10-11 10:57 ` Jørgen Kvalsvik
2022-10-11 11:27 ` Richard Biener
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=20221005120403.68935-1-jorgen.kvalsvik@woven-planet.global \
--to=jorgen.kvalsvik@woven-planet.global \
--cc=gcc-patches@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).