From: "Anthony PERARD" <anthony.perard@vates.tech>
To: "Volodymyr Babchuk" <Volodymyr_Babchuk@epam.com>
Cc: xen-devel@lists.xenproject.org,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Michal Orzel" <michal.orzel@amd.com>,
"Jan Beulich" <jbeulich@suse.com>,
"Julien Grall" <julien@xen.org>,
"Roger Pau Monné" <roger.pau@citrix.com>,
"Stefano Stabellini" <sstabellini@kernel.org>
Subject: Re: [PATCH v2 3/3] xen: debug: gcov: add condition coverage support
Date: Fri, 28 Mar 2025 14:27:28 +0000 [thread overview]
Message-ID: <Z-axzjh97dz021-T@l14> (raw)
In-Reply-To: <20250328121902.2134020-4-volodymyr_babchuk@epam.com>
On Fri, Mar 28, 2025 at 12:19:18PM +0000, Volodymyr Babchuk wrote:
> Condition coverage, also known as MC/DC (modified condition/decision
> coverage) is a coverage metric that tracks separate outcomes in
> boolean expressions.
>
> This patch adds CONFIG_CONDITION_COVERAGE option to enable MC/DC for
> GCC. Clang is not supported right now.
>
> Signed-off-by: Volodymyr Babchuk <volodymyr_babchuk@epam.com>
>
> ---
>
> Changes in v2:
> - Move gcc version check from .c file to Rules.mk (I can't find
> an easy way to check GCC version at Kconfig level)
It's very easy to do so, our Kconfig already look for GCC's version ;-)
The result isn't used yet in Kconfig, but it is in some C files and
Makefile.
You can simply do:
depends on GCC_VERSION > 140000
(instead of checking for CC_IS_CLANG, because GCC_VERSION would be 0
when clang is used)
But, do you really need to check for gcc's version? Is
-fcondition-coverage mean something different in previous version?
Cann't you actually just check if a feature is present in the CC been
used? It is rare to check for a particular version of a compiler and
instead check if it knows about a flags.
Cheers,
--
Anthony Perard | Vates XCP-ng Developer
XCP-ng & Xen Orchestra - Vates solutions
web: https://vates.tech
next prev parent reply other threads:[~2025-03-28 14:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-28 12:19 [PATCH v2 0/3] Enable MC/DC support for GCOV Volodymyr Babchuk
2025-03-28 12:19 ` [PATCH v2 3/3] xen: debug: gcov: add condition coverage support Volodymyr Babchuk
2025-03-28 13:08 ` Jan Beulich
2025-03-28 14:27 ` Anthony PERARD [this message]
2025-03-28 12:19 ` [PATCH v2 1/3] xen: gcov: add support for gcc 14 Volodymyr Babchuk
2025-03-28 13:05 ` Jan Beulich
2025-03-28 12:19 ` [PATCH v2 2/3] xen: x86: irq: use do-while loop in create_irq() Volodymyr Babchuk
2025-03-28 13:04 ` Jan Beulich
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=Z-axzjh97dz021-T@l14 \
--to=anthony.perard@vates.tech \
--cc=Volodymyr_Babchuk@epam.com \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.