Release CBMC 6.3.0 #8460
Merged
Release CBMC 6.3.0 #8460
+30
−2
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
This release addresses build failures on aarch64 (64-bit ARM) platforms (via PR diffblue#8366) and for some CMake configurations (via PR diffblue#8435). Users of loop invariants with dynamic frames have two changes to their user experience: 1) Users will no longer need to give unwinding specifications for `do { ... } while(0)` loops. 2) Loop invariants that are conjunctions will be turned into more fine-grained properties to ease debugging of loop invariants when they aren't successfully proved.
tautschnig
requested review from
peterschrammel,
a team,
TGWDB and
esteffin
as code owners
TGWDB
approved these changes
Sep 19, 2024
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #8460 +/- ##
========================================
Coverage 78.31% 78.31%
========================================
Files 1726 1726
Lines 188817 188817
Branches 18270 18270
========================================
Hits 147874 147874
Misses 40943 40943 ☔ View full report in Codecov by Sentry. |
rod-chapman
reviewed
Sep 19, 2024
| 2) Loop invariants that are conjunctions will be turned into more fine-grained properties to ease debugging of loop invariants when they aren't successfully proved. | ||
|
|
||
| ## What's Changed | ||
| * Contracts: always remove spurious do {... } while(0) loops by @tautschnig in https://github.com/diffblue/cbmc/pull/8459 |
There was a problem hiding this comment.
Tell the user why this is great... e.g. "Therefore, introducing a do { ... } while (0) loop, either explicitly or as the result of a macro, will not change the numbering of other loops, and therefore will not impact the setting of unwindsets for other loops."
There was a problem hiding this comment.
Or something like that...
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.
This release addresses build failures on aarch64 (64-bit ARM) platforms (via PR #8366) and for some CMake configurations (via PR #8435). Users of loop invariants with dynamic frames have two changes to their user experience:
do { ... } while(0)loops.fine-grained properties to ease debugging of loop invariants when
they aren't successfully proved.