- Feb 05, 2020
-
-
Those goals happen to be solvable by [done] as well, so use that. I also dropped some inconsistent line breaks.
-
- Nov 02, 2019
-
-
Robbert Krebbers authored
-
- Oct 14, 2019
-
-
Robbert Krebbers authored
-
- Oct 12, 2019
-
-
Robbert Krebbers authored
Also removed some admissible instances: - `Atomic s (ResolveProph (Val v1) (Val v2))` (this one was already admissible) - `Atomic s Skip` (became admissible due to the instance for β)
-
- Sep 13, 2019
-
-
Jacques-Henri Jourdan authored
The general idea is to first import/export modules which are further than the current one, and then import/export modules which are close dependencies. This commit tries to use the same order of imports for every file, and describes the convention in ProofGuide.md. There is one exception, where we do not follow said convention: in program_logic/weakestpre.v, using that order would break printing of texan triples (??).
-
- Aug 07, 2019
-
-
Ralf Jung authored
-
- Jul 01, 2019
- Jun 29, 2019
-
-
Ralf Jung authored
This also gets rid of [val_for_compare]-normalization; instead we introduce a [LitErased] literal that is suited for use by erasure theorems.
-
- Jun 24, 2019
- Jun 18, 2019
- Jun 15, 2019
-
-
Rodolphe Lepigre authored
-
- Jun 14, 2019
-
-
Ralf Jung authored
-
- Jun 13, 2019
-
-
Ralf Jung authored
-
- Jun 10, 2019
-
-
Robbert Krebbers authored
-
Robbert Krebbers authored
-
- Jun 03, 2019
-
-
Robbert Krebbers authored
-
Robbert Krebbers authored
-
Robbert Krebbers authored
-
Robbert Krebbers authored
-
-
- Jun 02, 2019
-
-
Ralf Jung authored
-
- May 31, 2019
-
-
Amin Timany authored
-
- Mar 22, 2019
-
-
Rodolphe Lepigre authored
-
- Mar 19, 2019
-
-
Rodolphe Lepigre authored
-
Rodolphe Lepigre authored
-
- Mar 14, 2019
-
-
Robbert Krebbers authored
-
- Mar 05, 2019
-
-
Ralf Jung authored
-
- Nov 29, 2018
-
-
Tej Chajed authored
Adding a hint without a database now triggers a deprecation warning in Coq master (https://github.com/coq/coq/pull/8987).
-
- Oct 31, 2018
-
-
Robbert Krebbers authored
-
Robbert Krebbers authored
-
Robbert Krebbers authored
This commit extends the state interpretation with an additional parameter to talk about the number of forked-off threads, and a fixed postcondition for each forked-off thread: state_interp : Λstate → list Λobservation → nat → iProp Σ; fork_post : iProp Σ; This way, instead of having `True` as the post-condition of `Fork`, one can have any post-condition, which is then recorded in the state interpretation. The point of keeping track of the postconditions of forked-off threads, is that we get an (additional) stronger adequacy theorem: Theorem wp_strong_all_adequacy Σ Λ `{invPreG Σ} s e σ1 v vs σ2 φ : (∀ `{Hinv : invG Σ} κs, (|={⊤}=> ∃ (stateI : state Λ → list (observation Λ) → nat → iProp Σ) (fork_post : iProp Σ), let _ : irisG Λ Σ := IrisG _ _ _ Hinv stateI fork_post in stateI σ1 κs 0 ∗ WP e @ s; ⊤ {{ v, let m := length vs in stateI σ2 [] m -∗ [∗] replicate m fork_post ={⊤,∅}=∗ ⌜ φ v ⌝ }})%I) → rtc erased_step ([e], σ1) (of_val <$> v :: vs, σ2) → φ v. The difference with the ordinary adequacy theorem is that this one only applies once all threads terminated. In this case, one gets back the post-conditions `[∗] replicate m fork_post` of all forked-off threads. In Iron we showed that we can use this mechanism to make sure that all resources are disposed of properly in the presence of fork-based concurrency.
-