================
@@ -983,7 +979,7 @@ void CodeGenPGO::mapRegionCounters(const Decl *D) {
// for most embedded applications. Setting a maximum value prevents the
// bitmap footprint from growing too large without the user's knowledge. In
// the future, this value could be adjusted with a command-line option.
- unsigned MCDCMaxConditions = (CGM.getCodeGenOpts().MCDCCoverage) ? 6 : 0;
+ unsigned MCDCMaxConditions = (CGM.getCodeGenOpts().MCDCCoverage) ? 32767 : 0;
----------------
Jugst3r wrote:
FYI in GNATcoverage, we actually have a
```
--path-count-limit POSITIVE
[instrument]
Limit beyond which enumeration of BDD paths stops. If a decision has more
paths in its BDD than the limit, MC/DC coverage will not be assessed for
that
decision, resulting in violations in the report.
```
It is probably better to have a limit in terms of paths in the BDD, rather than
number of conditions. What do you think?
https://github.com/llvm/llvm-project/pull/82448
_______________________________________________
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
