Provide Common Configurations #788
Merged
Conversation
This file contains hidden or 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
michael-schwarz
requested review from
jerhard,
sim642,
stilscher and
vesalvojdani
sim642
reviewed
Jul 19, 2022
Member
The options CI workflow already should do that. |
sim642
reviewed
Jul 21, 2022
sim642
approved these changes
Jul 25, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 provides three example configurations that someone new to Goblint might want to use.
very-precise.json: Enables some of the more expensive abstract domains and features, especially useful for smaller programsmedium-program.json: Enables some costly features, but staying away from the very expensive ones. This is very close to, e.g. the configuration we use for SV-COMPlarge-programs.json: Minimal configuration for larger programs, should run fast even for large programs, but usually needs to be made more precise by adding further features. (based on ourzstdconfig)I came up with these configurations more or less off the top of my head, feel free to suggest tweaks! Are there any other common configurations that we want to offer?
The configs are validated as part of our regression tests, so they do not become stale. The symlink for the tests is needed such that both
regtest.shandupdate_suitefind the configuration file where they expect it to be.Closes #14