Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
Iris
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Model registry
Operate
Terraform modules
Monitor
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Pierre Roux
Iris
Commits
2c063fd4
Commit
2c063fd4
authored
4 years ago
by
Ralf Jung
Browse files
Options
Downloads
Patches
Plain Diff
note some design choices
parent
522e0304
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
theories/heap_lang/lang.v
+7
-0
7 additions, 0 deletions
theories/heap_lang/lang.v
with
7 additions
and
0 deletions
theories/heap_lang/lang.v
+
7
−
0
View file @
2c063fd4
...
@@ -15,6 +15,13 @@ Noteworthy design choices:
...
@@ -15,6 +15,13 @@ Noteworthy design choices:
[b] are evaluated. With left-to-right evaluation, that triple is basically
[b] are evaluated. With left-to-right evaluation, that triple is basically
useless unless the user let-expands [b].
useless unless the user let-expands [b].
- Even after deallocating a location, the heap remembers that these locations
were previously allocated and makes sure they do not get reused. This is
necessary to ensure soundness of the [meta] feature provided by [gen_heap].
Also, unlike in langauges like C, allocated and deallocated "blocks" do not
have to match up: you can allocate a large array of locations and then
deallocate a hole out of it in the middle.
- For prophecy variables, we annotate the reduction steps with an "observation"
- For prophecy variables, we annotate the reduction steps with an "observation"
and tweak adequacy such that WP knows all future observations. There is
and tweak adequacy such that WP knows all future observations. There is
another possible choice: Use non-deterministic choice when creating a prophecy
another possible choice: Use non-deterministic choice when creating a prophecy
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment