Skip to content

SVA-to-LTL: sequence and/or #1114

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
May 22, 2025
Merged

SVA-to-LTL: sequence and/or #1114

merged 1 commit into from
May 22, 2025

Conversation

kroening
Copy link
Member

This adds SVA sequence and/or to the SVA-to-LTL translator.

@kroening kroening marked this pull request as ready for review May 18, 2025 20:12
@kroening kroening force-pushed the sva-to-ltl-and-or branch 2 times, most recently from 732c554 to 67d142d Compare May 18, 2025 20:59
@tautschnig
Copy link
Collaborator

Needs git conflict resolution.

This adds SVA sequence and/or to the SVA-to-LTL translator.
@kroening kroening force-pushed the sva-to-ltl-and-or branch from 67d142d to fbbe228 Compare May 21, 2025 08:53
@kroening
Copy link
Member Author

Needs git conflict resolution.

Done

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.

I am assuming the complexity of the ID_sva_and case is just unavoidable (or maybe those matches are always small?).

@kroening
Copy link
Member Author

I am assuming the complexity of the ID_sva_and case is just unavoidable (or maybe those matches are always small?).

The real answer is to make an automaton, and merge that with the model. I don't see a better way when the goal is "readable, equivalent LTL".

@kroening kroening merged commit 2728d52 into main May 22, 2025
9 checks passed
@kroening kroening deleted the sva-to-ltl-and-or branch May 22, 2025 05:15
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