public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Jørgen Kvalsvik" <j@lambda.is>
To: gcc-patches@gcc.gnu.org
Cc: hubicka@ucw.cz, "Jørgen Kvalsvik" <j@lambda.is>
Subject: [PATCH 0/3] Condition coverage docs, bugfix
Date: Tue, 25 Jun 2024 10:03:29 +0200	[thread overview]
Message-ID: <20240625080332.1517736-1-j@lambda.is> (raw)


This patch set includes a memory leak fix and some documentation
additions for condition coverage. Without prior knowledge it would be
hard to find out what exactly gcc/gcov means by "condition coverage",
so I fleshed it out and made sure to include some searchable keywords --
masking, MC/DC. The flags leave room for other condition coverage
flavors, and relies on docs to make it clear.

Jørgen Kvalsvik (3):
  Release structures on function return
  Add section on MC/DC in gcov manual
  Use the term MC/DC in help for gcov --conditions

 gcc/doc/gcov.texi   | 72 +++++++++++++++++++++++++++++++++++++++++++++
 gcc/gcov.cc         |  2 +-
 gcc/tree-profile.cc |  3 ++
 3 files changed, 76 insertions(+), 1 deletion(-)

-- 
2.39.2


             reply	other threads:[~2024-06-25  8:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-25  8:03 Jørgen Kvalsvik [this message]
2024-06-25  8:03 ` [PATCH 1/3] Release structures on function return Jørgen Kvalsvik
2024-06-25 10:23   ` Jan Hubicka
2024-06-25 10:37     ` Jørgen Kvalsvik
2024-06-26 10:20     ` Jørgen Kvalsvik
2024-06-27  6:26     ` Jørgen Kvalsvik
2024-06-25  8:03 ` [PATCH 2/3] Add section on MC/DC in gcov manual Jørgen Kvalsvik
2024-06-25 10:23   ` Jan Hubicka
2024-06-26 10:21     ` Jørgen Kvalsvik
2024-06-25  8:03 ` [PATCH 3/3] Use the term MC/DC in help for gcov --conditions Jørgen Kvalsvik
2024-06-25 10:25   ` Jan Hubicka
2024-06-25 10:42     ` Jørgen Kvalsvik
2024-06-26 10:21     ` Jørgen Kvalsvik

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=20240625080332.1517736-1-j@lambda.is \
    --to=j@lambda.is \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hubicka@ucw.cz \
    /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).