Fix Not_found exception in autotuner with congruences and termination.
#1271
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
|
I started a run (termination only) of this on |
michael-schwarz
approved these changes
Nov 23, 2023
|
With this PR we now succeed on 618 termination tasks. It should have no influence on other tasks. |
…e domain when termination was enabled
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Previously, there a
Not_foundexception was raised by the autotuner when it tried to activate thecongruencedomain for the__goblint_boundedfunction used in the termination analysis, as thefundecfor this function could not be found.This PR fixes this, by catching the exception, and not trying to enable the
congruencedomain for functions for which there are no declarations.