On 6/25/24 12:25, Jan Hubicka wrote:
Without key terms like "masking" and "MC/DC" it is not at all obvious what --conditions actually reports on, and there is no easy path for the user to figure out. By at least including the two key terms MC/DC and masking users have something to search for.gcc/ChangeLog: * gcov.cc (print_usage): Reference masking MC/DC.So the main purpose is to turn users into masking MC/DC description in the manual? Asking google does not seem to do the trick so far, but I don't know if better options.
Either in the manual (which has a very brief example), or into google to find random blog posts or papers like An Investigation of Three Forms of the Modified Condition Decision Coverage (MCDC) Criterion by Chilenski (2001) and https://ntrs.nasa.gov/api/citations/20040086014/downloads/20040086014.pdf (a tutorial on MC/DC by Hayhurst et al). Granted, the web is a bit sparse on anything beyond trivial (and usually quietly unique cause) MC/DC examples, but I'm not sure if the gcc/gcov manual is the home for it.
Thanks, Jørgen
OK, Thanks--- gcc/gcov.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gcc/gcov.cc b/gcc/gcov.cc index f6787f0be8f..1e2e193d79d 100644 --- a/gcc/gcov.cc +++ b/gcc/gcov.cc @@ -1015,7 +1015,7 @@ print_usage (int error_p) fnotice (file, " -c, --branch-counts Output counts of branches taken\n\ rather than percentages\n"); fnotice (file, " -g, --conditions Include modified condition/decision\n\ - coverage in output\n"); + coverage (masking MC/DC) in output\n"); fnotice (file, " -d, --display-progress Display progress information\n"); fnotice (file, " -D, --debug Display debugging dumps\n"); fnotice (file, " -f, --function-summaries Output summaries for each function\n"); -- 2.39.2
