mirror of
https://github.com/Z3Prover/z3
synced 2025-04-24 17:45:32 +00:00
stats, comment
This commit is contained in:
parent
f1ce0e233a
commit
0ff87a9943
2 changed files with 1 additions and 6 deletions
|
@ -16,11 +16,6 @@ Notes:
|
|||
|
||||
TODO: try a final core reduction step or other core minimization
|
||||
|
||||
TODO: fallback lemma is redundant:
|
||||
The core lemma uses m_vars and m_conflict directly instead of walking the stack.
|
||||
It should be an invariant that the core is false (the negation of the core is valid modulo assertions).
|
||||
The fallback lemma prunes at least the last value assignment.
|
||||
|
||||
TODO: If we have e.g. 4x+y=2 and y=0, then we have a conflict no matter the value of x, so we should drop x=? from the core.
|
||||
(works currently if x is unassigned; for other cases we would need extra info from constraint::is_currently_false)
|
||||
|
||||
|
|
|
@ -68,7 +68,7 @@ namespace polysat {
|
|||
pvar conflict_var() const { return m_conflict_var; }
|
||||
|
||||
bool is_bailout() const { return m_bailout; }
|
||||
void set_bailout() { SASSERT(!is_bailout()); m_bailout = true; }
|
||||
void set_bailout() { SASSERT(!is_bailout()); m_bailout = true; s().m_stats.m_num_bailouts++; }
|
||||
|
||||
bool empty() const {
|
||||
return m_constraints.empty() && m_vars.empty() && m_literals.empty() && m_conflict_var == null_var;
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue