Skip to content

bugfix for SVA cover #1068

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

Merged
merged 1 commit into from
Apr 22, 2025
Merged

bugfix for SVA cover #1068

merged 1 commit into from
Apr 22, 2025

Conversation

kroening
Copy link
Member

This changes the implicit 'always' used for SVA cover properties from LTL G to SVA always. This avoids a mixture of LTL and SVA, which is not supported by the BMC backend.

@kroening kroening marked this pull request as ready for review April 18, 2025 13:57
@kroening kroening force-pushed the cover_sequence1 branch 2 times, most recently from b0f94a4 to 29b70bf Compare April 18, 2025 16:17
@@ -119,7 +119,7 @@ exprt normalize_property(exprt expr)
{
// top-level only
if(expr.id() == ID_sva_cover)
expr = G_exprt{not_exprt{to_sva_cover_expr(expr).op()}};
expr = sva_always_exprt{not_exprt{to_sva_cover_expr(expr).op()}};
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we were missing the corresponding comment in normalize_property.h -- would you mind adding that one?

This changes the implicit 'always' used for SVA cover properties from LTL G
to SVA always.  This avoids a mixture of LTL and SVA, which is not supported
by the BMC backend.
@kroening kroening merged commit 6dde22a into main Apr 22, 2025
9 checks passed
@kroening kroening deleted the cover_sequence1 branch April 22, 2025 15:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants