-
Notifications
You must be signed in to change notification settings - Fork 121
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
sail-to-lean: Add support to memory #959
Comments
Is |
The memory interface in Sail uses bitvectors for physical addresses, FWIW. |
LNSym did the same, AFAIU. |
But it's Nat's in the Coq (sequential) state, right? In Module NMap := FMapAVL.Make(OrderedTypeEx.N_as_OT).
Definition Memstate : Type := NMap.t memory_byte. |
Yes, it is there. With the new concurrency interface the model's type is passed down (and I think Thibaut's sequential interpretation uses that directly, even though the Sail interface requires a function to embed it in a bitvector). It probably doesn't make much difference for us at the moment. |
Removes the previous hack of just using StateM Unit in this case. This will be necessary to proceed with #959 on examples that use memory but no registers.
This is a prerequisite for properly fixing #939.
A good candidate would be to have the
SequentialState.mem
field be aStd.HashMap Nat UInt8
The text was updated successfully, but these errors were encountered: