public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "j at lambda dot is" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug gcov-profile/115047] Inconsistent MC/DC reported by GCC and LLVM Date: Mon, 13 May 2024 18:51:12 +0000 [thread overview] Message-ID: <bug-115047-4-Zo7970e2Dk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-115047-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115047 --- Comment #1 from Jørgen Kvalsvik <j at lambda dot is> --- gcc is not wrong here - f(1, 0, 0) = false, while f(1, 0, 1) = true so clearly c has an independent effect on the outcome here, and both its values has been observed. I think clang measures unique-cause and not masking MC/DC which probably explains the difference (at least clang's documentation [1] does not specify which form it measures. Since more than one variable change between the two test vectors I assume that would be it. I don't have clang 19 available right now, does f(0, 0, 1); f(0, 0, 0); cover c? [1] https://clang.llvm.org/docs/SourceBasedCodeCoverage.html#mc-dc-instrumentation
next prev parent reply other threads:[~2024-05-13 18:51 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-12 7:44 [Bug gcov-profile/115047] New: " wentaoz5 at illinois dot edu 2024-05-13 18:51 ` j at lambda dot is [this message] 2024-05-13 19:10 ` [Bug gcov-profile/115047] " j at lambda dot is 2024-06-05 5:29 ` wentaoz5 at illinois dot edu
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=bug-115047-4-Zo7970e2Dk@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).