Skip to content

BDD engine: only look for atomic propositions in supported properties #1043

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 4, 2025

Conversation

kroening
Copy link
Member

The BDD engine is changed to avoid searching unsupported properties for atomic propositions.

@kroening kroening force-pushed the bdd-property-supported branch from 07e760f to 92595b3 Compare March 30, 2025 02:18
@kroening kroening marked this pull request as ready for review March 30, 2025 02:27
Comment on lines +507 to +512
if(!property_supported(property.normalized_expr))
{
property.failure("property not supported by BDD engine");
return;
}

Copy link
Collaborator

Choose a reason for hiding this comment

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

Should the code that follows (the code that actually does the transform to CTL) be combined with the property_supported code? That is, should property_supported right away do the transform?

Copy link
Member Author

Choose a reason for hiding this comment

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

The duplication is also bugging me, but it seems even less desirable to make the creation of some new data structure a side-effect of property_supported.

Copy link
Collaborator

Choose a reason for hiding this comment

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

How about making property_supported (though then perhaps by the name of make_CTL_property or the likes) return a std::optional<exprt> where an unsupported property would cause {} to be returned?

Copy link
Member Author

Choose a reason for hiding this comment

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

Coming with #1051

Comment on lines +13 to +16
bool is_AGp(const exprt &expr)
{
return expr.id() == ID_AG && !has_temporal_operator(to_AG_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.

Surprisingly, this is different from is_AGp in bdd_enginet::check_property?!

Copy link
Member Author

Choose a reason for hiding this comment

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

Now clearer, avoiding labeling expressions as AGp that are just equivalent.

@kroening kroening force-pushed the bdd-property-supported branch from 92595b3 to 5196b58 Compare March 31, 2025 21:07
The BDD engine is changed to avoid searching unsupported properties for
atomic propositions.
@kroening kroening force-pushed the bdd-property-supported branch from 5196b58 to 6bc4a23 Compare April 1, 2025 14:06
Copy link
Collaborator

@tautschnig tautschnig left a comment

Choose a reason for hiding this comment

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

Approving with the assumption that #1051 will bring about further improvements.

@tautschnig tautschnig merged commit ed453c4 into main Apr 4, 2025
9 checks passed
@tautschnig tautschnig deleted the bdd-property-supported branch April 4, 2025 14:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants