-
Notifications
You must be signed in to change notification settings - Fork 86
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
How to verify mmio access? #1304
Comments
As far as Kani knows, this is an illegal access to unallocated memory, which Kani is correctly catching. It should be possible as a feature enhancement for Kani to allow specification of memory areas as MMIO. changing tag to feature request. |
CBMC support for mmio seems to be in flux, and the "new approach" has yet to be merged: |
Notes on CBMC's mmio implementation. It doesn't int main()
{
int *p=0x10;
int *q=0x20;
*p=42;
assert(*p==42);
int old = *q;
int old2 = *q;
assert(old == old2);
return 0;
}
|
#1328 is still blocked by CBMC's diffblue/cbmc#6747 |
I've tried with the below code for mocking a mmio access.
using the following command line invocation:
with Kani version: 0.3.0
It brought out the following failures.
Why did the verification failures occur and how to pass the verification when an object of absolute address (e.g., mmio) is involved?
The text was updated successfully, but these errors were encountered: