Skip to content

Fix setup_relevancy for relevancy-dependent case split strategies #7662

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
NikolajBjorner merged 1 commit into from
May 27, 2025
Merged

Fix setup_relevancy for relevancy-dependent case split strategies #7662

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions src/smt/smt_setup.cpp
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -834,6 +834,13 @@ namespace smt {
// there are some other cases where relevancy propagation is harmful.
//
void setup::setup_relevancy(static_features& st) {
// the case split queue has been constructed by now.
// it is not safe to disable relevancy if the case split stragegy is relevancy-dependent.
if (m_params.m_case_split_strategy == CS_RELEVANCY ||
m_params.m_case_split_strategy == CS_RELEVANCY_ACTIVITY ||
m_params.m_case_split_strategy == CS_RELEVANCY_GOAL)
return;

if (st.m_has_bv && !st.m_has_fpa && st.m_num_quantifiers == 0)
m_params.m_relevancy_lvl = 0;
}
Expand Down