forked from OSchip/llvm-project
[analyzer][NFC] Add LLVM_UNLIKELY to assumeDualImpl
Aligned with the measures we had in D124674, this condition seems to be unlikely. Nevertheless, I've made some new measurments with stats just for this, and data confirms this is indeed unlikely. Differential Revision: https://reviews.llvm.org/D127190
This commit is contained in:
parent
aa9b3389ff
commit
17e9ea6138
|
@ -47,7 +47,7 @@ template <typename AssumeFunction>
|
||||||
ConstraintManager::ProgramStatePair
|
ConstraintManager::ProgramStatePair
|
||||||
ConstraintManager::assumeDualImpl(ProgramStateRef &State,
|
ConstraintManager::assumeDualImpl(ProgramStateRef &State,
|
||||||
AssumeFunction &Assume) {
|
AssumeFunction &Assume) {
|
||||||
if (State->isPosteriorlyOverconstrained())
|
if (LLVM_UNLIKELY(State->isPosteriorlyOverconstrained()))
|
||||||
return {State, State};
|
return {State, State};
|
||||||
|
|
||||||
// Assume functions might recurse (see `reAssume` or `tryRearrange`). During
|
// Assume functions might recurse (see `reAssume` or `tryRearrange`). During
|
||||||
|
|
Loading…
Reference in New Issue