-
Notifications
You must be signed in to change notification settings - Fork 97
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kani fails to detect for loop bound after upgrade to nightly-2024-03-15 #3088
Comments
celinval
added
[C] Bug
This is a bug. Something isn't working.
T-High Priority
Tag issues that have high priority
labels
Mar 18, 2024
celinval
added a commit
that referenced
this issue
Mar 18, 2024
Note that with this upgrade Kani can no longer automatically detect loop bounds when using range. For more details, see: #3088
This appears to also affect incredibly simple cases like: #[kani::proof]
fn check() {
for _ in 0..1 {}
} Note |
With apologies for not actually posting on this issue: diffblue/cbmc#8247 fixes this problem on the CBMC side. We just need to get this merged plus a new CBMC release to be produced. |
tautschnig
added a commit
to tautschnig/kani
that referenced
this issue
Aug 1, 2024
CBMC v6 includes diffblue/cbmc#8247, which fixes the need for unwind attributes that were newly found to be necessary when upgrading to nightly-2024-03-15 (model-checking#3084). Resolves: model-checking#3088
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
While upgrading to nightly-2024-03-15, we had to add a few
#[kani::unwind]
attributes to harnesses with for loops with simple integer ranges. We need to investigate why this is no longer the case, and hopefully improve the loop bound detection algorithm.Here is an example of a test case (tests/expected/iterator/main.rs):
using the following command line invocation:
with Kani version: #3084
I expected to see this happen: Kani should be able to automatically detect the loop bound.
Instead, this happened: Kani requires an unwind attribute.
The text was updated successfully, but these errors were encountered: