From: "Martin Liška" <mliska@suse.cz>
To: "Jørgen Kvalsvik" <jorgen.kvalsvik@woven-planet.global>,
gcc-patches@gcc.gnu.org
Subject: Re: Ping [PATCH] Add condition coverage profiling
Date: Thu, 27 Oct 2022 12:34:46 +0200 [thread overview]
Message-ID: <8b6262df-6c48-1ad6-9944-2530f69fbf68@suse.cz> (raw)
In-Reply-To: <b920e748-b649-d35a-8100-4c0a6a09581a@woven-planet.global>
On 10/25/22 08:33, Jørgen Kvalsvik wrote:
> Gentle ping. I have a tuned the summary output slightly (decisions covered ->
> condition outcomes covered) already.
Sorry for a small delay, I'm working on it.
One general issue I noticed is you use an invalid coding style, where you use 4 spaces
for each level. Plus see the indentation for '{', '}':
diff --git a/gcc/tree-profile.cc b/gcc/tree-profile.cc
index 0b537d64d97..b661ed92045 100644
--- a/gcc/tree-profile.cc
+++ b/gcc/tree-profile.cc
@@ -553,11 +553,12 @@ masking_vectors (conds_ctx& ctx, array_slice<basic_block> blocks,
body[0] = body.pop ();
for (const basic_block b : body)
- {
+ {
for (edge e1 : b->preds)
- for (edge e2 : b->preds)
- {
- const basic_block top = e1->src;
+ for (edge e2 : b->preds)
+ {
+ const basic_block top = e1->src;
+...
const basic_block bot = e2->src;
const unsigned cond = e1->flags & e2->flags & (EDGE_CONDITION);
Link: https://gcc.gnu.org/codingconventions.html
What editor do you use?
Cheers,
Martin
next prev parent reply other threads:[~2022-10-27 10:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 10:16 Jørgen Kvalsvik
2022-10-18 0:17 ` Hans-Peter Nilsson
2022-10-18 10:13 ` Jørgen Kvalsvik
2022-10-25 6:33 ` Ping " Jørgen Kvalsvik
2022-10-27 10:34 ` Martin Liška [this message]
2022-11-02 6:16 ` Jørgen Kvalsvik
2022-11-09 20:08 ` [Ping 2][PATCH] " Jørgen Kvalsvik
2022-11-10 14:19 ` Ping [PATCH] " 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=8b6262df-6c48-1ad6-9944-2530f69fbf68@suse.cz \
--to=mliska@suse.cz \
--cc=gcc-patches@gcc.gnu.org \
--cc=jorgen.kvalsvik@woven-planet.global \
/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).