-
Notifications
You must be signed in to change notification settings - Fork 15
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.
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
Problem with engine heuristic #921
Comments
kroening
added a commit
that referenced
this issue
Jan 6, 2025
The k-induction engine now correctly reports unsupported assumptions, and is then skipped by the engine selection heuristic. Fixes #921.
kroening
added a commit
that referenced
this issue
Jan 7, 2025
The k-induction engine now correctly reports unsupported assumptions, and is then skipped by the engine selection heuristic. Fixes #921.
May I ask you to try #923 ? |
Yep! It's working on my side. Thanks a lot. To be sure, I just want to point out that before this modification, in case of an unsupported assumption, the k-induction engine would attempt to prove the property without the assumption. However, now it seems the engine always returns "UNKNOWN" in such cases. This convention can make sense. Is it the intended behavior? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The new basic engine heuristic seems to introduce a bug when it is applied to designs containing assumptions not supported by the k-induction engine (temporal property in my case). The assumption seems to be transformed into an assertion.
As an example, if you take
regression/ebmc/k-induction/ring_buffer.sv
, and you slightly modify the first assumption in order to add a temporal operator as follows, the engine will outputREFUTED
instead ofASSUMED
orFAILURE: property unsupported by k-induction
for the first assumption:The text was updated successfully, but these errors were encountered: