Remove fixed malloc wrappers from svcomp conf#1592
Merged
Conversation
sim642
added
cleanup
michael-schwarz
approved these changes
Oct 4, 2024
14 tasks
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
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 list was based on one from CPAchecker and over time extended, but that was all before we had the autotuner for malloc wrappers.
I did some full resources runs some time ago and found that they make absolutely no difference: we lost one task on the entire SV-COMP suite. And even that's just noise: there were some tasks flipping to true and others flipping from true, canceling them out (timeouts and segfaults).
It also makes us look very bad, fingerprinting tasks when it's not even useful...