Make sem.malloc.* explicit in svcomp confs
#1885
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
This is likely to change in the future, so it's better for the old reference confs to be explicit about it. More importantly, PR #1777 changed the default behavior of malloc(0) which accidentally affected svcomp26.
Member
Author
On level01 with 60s and 1GB this affected three tasks:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 is likely to change in the future, so it's better for the old reference confs to be explicit about it.
More importantly, PR #1777 changed the default behavior of
malloc(0)which accidentally affected svcomp26. We made the default sound (unlikesem.malloc.fail) but didn't override it for svcomp26. Hopefully this oversight doesn't cost us too many points...