This repository has been archived by the owner on Oct 14, 2022. It is now read-only.
flow_insensitive_invariant YAML entry type
#63
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-authored-by: Sven Umbricht <[email protected]>
The schema workflow command outputs there instead of the project root.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This depends on #61 being merged, the PR diff currently isn't nice, but a nicer diff can be seen here: sim642/sv-witnesses@yaml-schema...goblint:sv-witnesses:flow_insensitive_invariant.
While loop invariants and location invariants (#62) are associated with particular program locations where the program flow reaches, there are also flow-insensitive invariants which hold throughout the program execution. This location-less entry type is just for that.
In Goblint we could particularly use these for such invariants in multithreaded programs: goblint/analyzer#830.
TODO
invariant_certificateentry type fromlocation_invariantYAML entry type as schema #62 would also apply to these, but I've avoided duplicating the same generalization here.