Skip to content
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

Proper multi-property SV-COMP specification #1220

Closed
sim642 opened this issue Oct 20, 2023 · 1 comment · Fixed by #1228
Closed

Proper multi-property SV-COMP specification #1220

sim642 opened this issue Oct 20, 2023 · 1 comment · Fixed by #1228
Assignees
Milestone

Comments

@sim642
Copy link
Member

sim642 commented Oct 20, 2023

In #1201 (and maybe something earlier as well), preliminary and hacky support for SV-COMP MemSafety was added. That category uses a specification file with multiple properties but our implementation only does one at a time. It should be cleaned up.

Since our analysis isn't property-directed anyway, we can just be very general and allow other combinations just as well.

@sim642 sim642 added this to the SV-COMP 2024 milestone Oct 20, 2023
@sim642 sim642 self-assigned this Oct 20, 2023
@sim642
Copy link
Member Author

sim642 commented Oct 31, 2023

This is blocked by the MemSafety analyses not working at all: #1201 (comment).

sim642 added a commit to sim642/opam-repository that referenced this issue Nov 24, 2023
nberth pushed a commit to nberth/opam-repository that referenced this issue Jun 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant