[all-commits] [llvm/llvm-project] e7f742: [compiler-rt] Add print_coverage_summary to silenc...

[Manuel Carrasco via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: e7f7422a14cfdd6d00fcf7e2e25bfd5a47897030
      https://github.com/llvm/llvm-project/commit/e7f7422a14cfdd6d00fcf7e2e25bfd5a47897030
  Author: Manuel Carrasco <Manuel.Carrasco at amd.com>
  Date:   2026-10-02 (Fri, 02 Oct 2026)

  Changed paths:
    M clang/docs/SanitizerCoverage.md
    M compiler-rt/lib/sanitizer_common/sanitizer_coverage_fuchsia.cpp
    M compiler-rt/lib/sanitizer_common/sanitizer_coverage_libcdep_new.cpp
    M compiler-rt/lib/sanitizer_common/sanitizer_flags.inc
    A compiler-rt/test/sanitizer_common/TestCases/sanitizer_coverage_summary.cpp

  Log Message:
  -----------
  [compiler-rt] Add print_coverage_summary to silence SanitizerCoverage dump logs (#228039)

When running a test suite of SanitizerCoverage-instrumented binaries,
the `SanitizerCoverage: … PCs written` summary on stderr can poison
FileCheck and cause unexpected failures.

There is no way to turn that print off today. At most you can use
`log_path`, but that still creates a text file per process. We could
have guard it on the verbosity option, but that would change the default
and may regress consumers that rely on this output.

This PR adds `print_coverage_summary` (default true). Set
`print_coverage_summary=0` to keep the dump log disable; .sancov files
are still written. The same guard is used on the Fuchsia path.

The new lit test is a copy of sanitizer_coverage_trace_pc_guard.cpp,
adapted to check the default print and print_coverage_summary=0.



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications