https://bugs.llvm.org/show_bug.cgi?id=41533
Bug ID: 41533
Summary: llvm-cov: "counter mismatch" warnings are handled in
ambiguous way
Product: new-bugs
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: new bugs
Assignee: unassignedb...@nondot.org
Reporter: mmo...@google.com
CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org
This has bitten us several times, the most recent is in
https://github.com/google/oss-fuzz/issues/2330
The problem is that llvm-cov prints a warning, e.g.:
warning: /out/dumps/simple_round_trip.profdata: Function basic block count
change detected (counter mismatch)
and interrupts the execution. IMO it should be either of the following:
1) print an error and interrupt the execution
2) print a warning and continue the execution (if possible?)
Otherwise, we get just a warning but a significantly incomplete report (depends
on the timing / threading, if you're merging multiple dumps).
What do others think?
--
You are receiving this mail because:
You are on the CC list for the bug._______________________________________________
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
