VSD - correct widening merge to handle extreme values #6190
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.
During a widening merge, it is possible for the upper or lower bound to be extended to integer limits -
max_exprt(type)ormin_exprt(type). This was not handled gracefully and could have resulted in an (inappropriate) invariant violation constructing new intervals. Extreme values, along with overflow and underflow calculating new bounds, are now handled appropriately.