Interval: Don't compute on top values #134
Merged
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 introduces a fix so we no longer compute on
topvalues within the interval domain.The
topin the interval is actually represented by the interval[-2^31, 2^31-1]. As the concrete values for a integer might lie outside this range, we cannot compute with this value, because this could yield unsound results. So instead, if one of the operands of a binary/unary operation istop, the result of the operation will betop, too.Side note: Having a top value in an interval representation that is truly an over-approximation for all possible concrete values (including
-2^63,2^64-1) would require an implementation with arbitrary precision integers.