-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathHoare.thy
2071 lines (1802 loc) · 66.2 KB
/
Hoare.thy
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
theory Hoare
imports Main Imp begin
(*
(** * Hoare: Hoare Logic *)
(* Version of 5/5/2010 *)
Require Export Imp.
(** In the past two chapters, we've begun applying the mathematical
tools developed in the first part of the course to studying the
theory of a small programming language, Imp.
- We defined a type of _abstract syntax trees_ for Imp, together
with an _evaluation relation_ (a partial function on states)
that specifies the _operational semantics_ of programs.
If the course had ended at this point, we would still have
gotten to something extremely useful: a set of tools for
defining and discussing programming languages and language
features that are mathematically precise, easy to work with, and
very flexible.
The language we defined, though small, captures some of the key
features of full-blown languages like C, C++, and Java,
including the fundamental notion of mutable state and some
common control structures.
- We proved a number of _metatheoretic properties_ -- "meta" in
the sense that they are properties of the language as a whole,
rather than properties of particular programs in the language.
These included:
- determinacy of evaluation
- equivalence of some different ways of writing down the
definition
- guaranteed termination of certain classes of programs
- correctness (in the sense of preserving behavioral
equivalence) of a number of useful program transformations.
All of these properties -- especially the behavioral
equivalences -- are things that language designers, compiler
writers, and users might care about knowing. Indeed, many of
them are so fundamental to our understanding of the programming
languages we deal with that we might not consciously recognize
them as "theorems." (But, as the discussion of
[subst_equiv_property] in Equiv.v showed, properties that seem
intuitively obvious can sometimes be quite subtle or, in some
cases, actually even wrong!)
We'll return to this theme later in the course when we discuss
_types_ and _type soundness_.
- We saw a couple of examples of _program verification_ -- using
the precise definition of Imp to prove formally that certain
particular programs (factorial and slow subtraction) satisfied
particular specifications of their behavior.
*)
(** In this chapter, we're going to take this idea further. We'll
develop a reasoning system called _Floyd-Hoare Logic_ -- usually,
if somewhat unfairly, shortened to just _Hoare Logic_ -- in which
each of the syntactic constructs of Imp is equipped with a single,
generic "proof rule" that can be used to reason about programs
involving this construct.
Hoare Logic originates in the 1960s, and it continues to be the
subject of intensive research right up to the present day. It
lies at the core of a huge variety of tools that are now being
used to specify and verify real software systems.
*)
(* ####################################################### *)
(** * Hoare Logic *)
(* ####################################################### *)
(** ** Assertions *)
(** If we're going to talk about specifications of programs, the first
thing we'll want is a way of making _assertions_ about properties
that hold at particular points in time -- i.e., properties that
may or may not be true of a given state. *)
Definition Assertion := state -> Prop.
*)
types assertion = "state \<Rightarrow> bool"
(*
(** **** Exercise: 1 star (assertions) *)
(** Paraphrase the following assertions in English.
[[
fun st => st X = 3
fun st => st X = x
fun st => st X <= st Y
fun st => st X = 3 \/ st X <= st Y
fun st => (st Z) * (st Z) <= x
/\ ~ (((S (st Z)) * (S (st Z))) <= x)
fun st => True
fun st => False
]]
*)
(** (Remember that one-star exercises do not need to be handed in.) *)
(** [] *)
(** This way of writing assertions is formally correct -- it precisely
captures what we mean, and it is exactly what we will use in Coq
proofs -- but it is not very nice to look at: every single
assertion that we ever write is going to begin with [fun st => ],
and everyplace we refer to a variable in the current state it is
written [st X].
Moreover, this is the _only_ way we use states and the only way we
refer to the values of variables in the current state: we never
need to talk about two states at the same time, etc. So when we
are writing down assertions informally, we can make some
simplifications: drop the initial [fun st =>] and write just [X]
instead of [st X]. *)
(** Informally, instead of
[[
fun st => (st Z) * (st Z) <= x
/\ ~ ((S (st Z)) * (S (st Z)) <= x)
]]
we'll write just
[[
Z * Z <= x
/\ ~((S Z) * (S Z) <= x).
]]
*)
(* ####################################################### *)
(** ** Hoare Triples *)
(** Next, we need a way of specifying -- making general claims
about -- the behavior of commands. Since we've defined assertions
as a way of making general claims about the properties of states,
and since the behavior of a command is to transform one state to
another, a general claim about a command takes the following form:
- "If [c] is started in a state satisfying assertion [P], and if
[c] eventually terminates, then the final state is guaranteed
to satisfy the assertion [Q]."
Such a claim is called a _Hoare Triple_. The property [P] is
called a _precondition_; [Q] is a _postcondition_.
Since we'll be working a lot with Hoare triples, it's useful to
have a compact notation:
[[
{{P}} c {{Q}}.
]]
Traditionally, Hoare triples are written [{P} c {Q}], but single
braces are already used for other things in Coq. *)
Definition hoare_triple (P:Assertion) (c:com) (Q:Assertion) : Prop :=
forall st st',
c / st ==> st' ->
P st ->
Q st'.
*)
definition hoare_triple :: "assertion \<Rightarrow> com \<Rightarrow> assertion \<Rightarrow> bool" ("{{_}} _ {{_}}") where
"{{P}} c {{Q}} \<equiv> (\<forall> st st'. ceval c st st' \<longrightarrow> P st \<longrightarrow> Q st')"
(*
Notation "{{ P }} c {{ Q }}" := (hoare_triple P c Q) (at level 90) : hoare_spec_scope.
Open Scope hoare_spec_scope.
(** **** Exercise: 1 star (triples) *)
(** Paraphrase the following Hoare triples in English.
[[
{{True}} c {{X = 5}}
{{X = x}} c {{X = x + 5)}}
{{X <= Y}} c {{Y <= X}}
{{True}} c {{False}}
{{X = x}}
c
{{Y = real_fact x}}.
{{True}}
c
{{(Z * Z) <= x /\ ~ (((S Z) * (S Z)) <= x)}}
]]
*)
(** [] *)
(** **** Exercise: 1 star (valid_triples) *)
(** Which of the following Hoare triples are _valid_ -- i.e., the
claimed relation between [P], [c], and [Q] is true?
[[
{{True}} X ::= 5 {{X = 5}}
{{X = 2}} X ::= X + 1 {{X = 3}}
{{True}} X ::= 5; Y ::= 0 {{X = 5}}
{{X = 2 /\ X = 3}} X ::= 5 {{X = 0}}
{{True}} SKIP {{False}}
{{False}} SKIP {{True}}
{{True}} WHILE True DO SKIP END {{False}}
{{X = 0}}
WHILE X == 0 DO X ::= X + 1 END
{{X = 1}}
{{X = 1}}
WHILE X <> 0 DO X ::= X + 1 END
{{X = 100}}
]]
(Note that we're using informal mathematical notations for
expressions inside of commands, for readability. We'll continue
doing so throughout the chapter.) *)
(** [] *)
(** To get us warmed up, here are two simple facts about Hoare
triples *)
Theorem hoare_post_true : forall (P Q : Assertion) c,
(forall st, Q st) ->
{{P}} c {{Q}}.
Proof.
intros P Q c H. unfold hoare_triple.
intros st st' Heval HP.
apply H. Qed.
*)
theorem hoare_post_true : "(\<forall> st. Q st) \<Longrightarrow> {{P}} c {{Q}}"
by (auto simp: hoare_triple_def)
theorem hoare_pre_false : "(\<forall> st. \<not>(P st)) \<Longrightarrow> {{P}} c {{Q}}"
by (auto simp: hoare_triple_def)
(*
Theorem hoare_pre_false : forall (P Q : Assertion) c,
(forall st, ~(P st)) ->
{{P}} c {{Q}}.
Proof.
intros P Q c H. unfold hoare_triple.
intros st st' Heval HP.
unfold not in H. apply H in HP.
destruct HP. Qed.
(* ####################################################### *)
(** ** Weakest Preconditions *)
(** That is, [P] suffices to guarantee that [Q] holds after [c],
and [P] is the weakest (easiest to satisfy) assertion that
guarantees [Q] after [c]. *)
(** **** Exercise: 1 star (wp) *)
(** What are the weakest preconditions of the following commands
for the following postconditions?
[[
{{ ? }} SKIP {{ X = 5 }}
{{ ? }} X ::= Y + Z {{ X = 5 }}
{{ ? }} X ::= Y {{ X = Y }}
{{ ? }}
IFB X == 0 THEN Y ::= Z + 1 ELSE Y ::= W + 2 FI
{{ Y = 5 }}
{{ ? }}
X ::= 5
{{ X = 0 }}
{{ ? }}
WHILE True DO X ::= 0 END
{{ X = 0 }}
]]
*)
(** [] *)
(* ####################################################### *)
(** ** Proof Rules *)
(* ####################################################### *)
(** *** Assignment *)
(** The rule for reasoning about assignment is the most basic of
the Hoare rules... and probably the trickiest! Here's how it
works.
Consider this (valid) Hoare triple:
[[
{{ Y = 1 }} X ::= Y {{ X = 1 }}
]]
In English: if we start out in a state where the value of [Y]
is [1] and we assign [Y] to [X], then we'll finish in a
state where [X] is [1]. That is, the property of being equal
to [1] gets transferred from [Y] to [X].
Similarly, in
[[
{{ Y + Z = 1 }} X ::= Y + Z {{ X = 1 }}
]]
the same property (being equal to one) gets transferred to
[X] from the expression [Y + Z] on the right-hand side of
the assignment.
More generally, if a is *any* arithmetic expression, then
[[
{{ a = 1 }} X ::= a {{ X = 1 }}
]]
is a valid Hoare triple.
Even more generally, if [Q] is *any* property of numbers and
[a] is any arithmetic expression, then
[[
{{ Q(a) }} X ::= a {{ Q(X) }}
]]
is a valid Hoare triple.
Rephrasing this a bit leads us to the general Hoare rule for
assignment:
[[
{{ Q where a is substituted for X }} X ::= a {{ Q }}
]]
This rule looks backwards to everyone at first -- what it's
saying is that, if Q holds in an environment where X is
replaced by the value of a, then Q still holds after
executing [X ::= a].
For example, these are valid applications of the assignment
rule:
[[
{{ X + 1 <= 5 }} X ::= X + 1 {{ X <= 5 }}
{{ 3 = 3 }} X ::= 3 {{ X = 3 }}
{{ 0 <= 3 /\ 3 <= 5 }} X ::= 3 {{ 0 <= X /\ X <= 5 }}
]]
*)
(** We could try to formalize the assignment rule directly in Coq
by treating [Q] as a family of assertions indexed by
arithmetic expressions -- something like this:
[[
Theorem hoare_asgn_firsttry :
forall (Q : aexp -> Assertion) V a,
{{fun st => Q a st}} (V ::= a) {{fun st => Q (AId V) st}}.
]]
But this formulation is not very nice, for two reasons.
First, it is not clear how we'd prove it is valid (we'd need
to somehow reason about all possible propositions). And
second, even if we could prove it, it would be awkward to
use.
A much smoother way of formalizing the rule arises from the
following obervation:
- For all states [st], "[Q] where a is substituted for [X]"
holds in the state [st] if and only if [Q] holds in the
state [update st X (aeval st a)]. *)
(** That is, asserting that a substituted variant of [Q] holds in
some state is the same as asserting that [Q] itself holds in
a substituted variant of the state. *)
(** Substitution: *)
Definition assn_sub V a Q : Assertion :=
fun (st : state) =>
Q (update st V (aeval st a)).
*)
definition assn_sub :: "id \<Rightarrow> aexp' \<Rightarrow> assertion \<Rightarrow> assertion" where
"assn_sub V a Q \<equiv> (\<lambda> st. Q (update st V (aeval' st a)))"
(*
(** The proof rule for assignment:
[[[
------------------------------
{{assn_sub V a Q}} V::=a {{Q}}
]]]
*)
Theorem hoare_asgn : forall Q V a,
{{assn_sub V a Q}} (V ::= a) {{Q}}.
Proof.
unfold hoare_triple.
intros Q V a st st' HE HQ.
inversion HE. subst.
unfold assn_sub in HQ. assumption. Qed.
*)
theorem hoare_asgn : "{{assn_sub V a Q}} (V ::= a) {{Q}}"
by (auto simp: assn_sub_def hoare_triple_def elim: ceval.cases)
(* CH: We don't actually need the full power of auto here.
once we apply the cases, we just finish every goal by simplification *)
theorem "{{assn_sub V a Q}} (V ::= a) {{Q}}"
unfolding assn_sub_def hoare_triple_def
apply clarsimp
apply (erule ceval.cases, simp+)
done
(*
(** Here's a first formal proof using this rule: *)
Example assn_sub_example :
{{fun st => 3 = 3}} (X ::= (ANum 3)) {{fun st => st X = 3}}.
Proof.
assert ((fun st => 3 = 3) =
(assn_sub X (ANum 3) (fun st => st X = 3))).
Case "Proof of assertion".
unfold assn_sub. reflexivity.
rewrite -> H. apply hoare_asgn. Qed.
*)
(* CH: here's a proof using hoare_asgn *)
lemma "{{\<lambda> st. (3 :: nat) = 3}} (X ::= (ANum' 3)) {{\<lambda> st. st X = 3}}"
apply (subgoal_tac "(\<lambda> st. (3 :: nat) = 3) = (assn_sub X (ANum' 3) (\<lambda> st. st X = 3))")
prefer 2
apply (simp add: assn_sub_def)
apply simp
apply (rule hoare_asgn)
done
(*
(** Unfortunately, the [hoare_asgn] rule doesn't literally apply
to the initial goal: it only works with triples whose
precondition has precisely the form [assn_sub Q V a] for some
[Q], [V], and [a]. So we start with asserting a little lemma
to get the goal into this form. *)
(** Doing this kind of fiddling with the goal state every time we
want to use [hoare_asgn] would get tiresome pretty quickly.
Fortunately, there are easier alternatives. One simple one is
to state a slightly more general theorem that introduces an
explicit equality hypothesis: *)
Theorem hoare_asgn_eq : forall Q Q' V a,
Q' = assn_sub V a Q ->
{{Q'}} (V ::= a) {{Q}}.
Proof.
intros Q Q' V a H. rewrite H. apply hoare_asgn. Qed.
*)
theorem hoare_asgn_eq : "Q' = assn_sub V a Q \<Longrightarrow> {{Q'}} (V ::= a) {{Q}}"
by (simp add: hoare_asgn)
(*
(** With this version of [hoare_asgn], we can do the proof much
more smoothly. *)
Example assn_sub_example' :
{{fun st => 3 = 3}} (X ::= (ANum 3)) {{fun st => st X = 3}}.
Proof.
apply hoare_asgn_eq. reflexivity. Qed.
*)
lemma "{{\<lambda> st. (3::nat)=3}} (X ::= (ANum' 3)) {{\<lambda> st. st X = 3}}"
by (rule hoare_asgn_eq, simp add: assn_sub_def)
(*
(** **** Exercise: 2 stars (hoare_asgn_examples) *)
(** Translate these informal Hoare triples
[[
{{ X + 1 <= 5 }} X ::= X + 1 {{ X <= 5 }}
{{ 0 <= 3 /\ 3 <= 5 }} X ::= 3 {{ 0 <= X /\ X <= 5 }}
]]
into formal statements and use [hoare_asgn_eq] to prove
them. *)
(* SOLUTION: *)
Example assn_sub_ex1 :
{{ fun st => st X + 1 <= 5 }}
(X ::= APlus (AId X) (ANum 1))
{{ fun st => st X <= 5 }}.
Proof.
apply hoare_asgn_eq. reflexivity. Qed.
Example assn_sub_ex2 :
{{ fun st => 0 <= 3 /\ 3 <= 5 }}
(X ::= (ANum 3))
{{ fun st => 0 <= st X /\ st X <= 5 }}.
Proof.
apply hoare_asgn_eq. reflexivity. Qed.
(** [] *)
(** **** Exercise: 3 stars (hoarestate2) *)
(** If the assignment rule still seems "backward", it may help to
think a little about alternative "forward" rules. Here is a
seemingly natural one:
[[
{{ True }} X ::= a {{ X = a }}
]]
Explain what is wrong with this rule.
(* SOLUTION: *)
The underlying problem is that the state in which the
postcondition will be checked is different than the state in which
[a] was evaluated when it was assigned to [X]. If [a] itself
mentions [X], then the value of [a] may be different in the final
state because of this update. (For example, if [Q] is [[a] is [X
+ 1], then setting [X] to [a] certainly does not achieve the
postcondition [X = X + 1]!) Another problem is that the rule
achieves _only_ the postcondition [X = a]. It tells us nothing
about any other facts that might have been true about the initial
state and would still be true in the final state (because they had
to do with different variables, for example). So this rule would
not be useful in reasoning about compound programs.
*)
(** [] *)
*)
theorem hoare_asgn_weakest : "{{P}} (V ::= a) {{Q}} \<Longrightarrow> (\<forall> st. P st \<longrightarrow> assn_sub V a Q st)"
by (auto simp: assn_sub_def hoare_triple_def)
theorem "{{P}} (V ::=a) {{Q}} \<Longrightarrow> (\<forall> st. P st \<longrightarrow> assn_sub V a Q st)"
unfolding hoare_triple_def assn_sub_def
apply clarsimp
apply (erule_tac x="st" in allE)
apply (erule_tac x="update st V (aeval' st a)" in allE)
apply (subgoal_tac "ceval (V ::= a) st (update st V (aeval' st a))")
apply simp
apply (rule E_Ass, simp)
done
(*
(** **** Exercise: 2 stars, optional (hoare_asgn_weakest) *)
(** The precondition in the rule hoare_asgn is in fact the weakest
precondition.
*)
Theorem hoare_asgn_weakest : forall P V a Q,
{{P}} (V ::= a) {{Q}} ->
forall st, P st -> assn_sub V a Q st.
Proof.
(* SOLUTION: *)
unfold hoare_triple.
intros P V a Q HE st H1.
unfold assn_sub.
apply HE with (st:=st).
apply E_Ass. reflexivity.
assumption.
Qed.
(* [] *)
(* ####################################################### *)
(** *** Consequence *)
(** The above discussion about the awkwardness of applying the
assignment rule illustrates a more general point: sometimes
the preconditions and postconditions we get from the Hoare
rules won't quite be the ones we want -- they may (as in the
above example) be logically equivalent but have a different
syntactic form that fails to unify with the goal we are
trying to prove, or they actually may be logically weaker or
stronger than the goal.
For instance, while
[[
{{3 = 3}} X ::= 3 {{X = 3}},
]]
is a valid Hoare triple, what we probably have in mind when
we think about the effect of this assignment is something
more like this:
[[
{{True}} X ::= 3 {{X = 3}}.
]]
This triple is also valid, but we can't derive it from
[hoare_asgn] (or [hoare_asgn_eq]) because [True] and [3 = 3]
are not equal, even after simplification.
In general, if we can derive [{{P}} c {{Q}}], it is valid to
change [P] to [P'] as long as [P'] is still enough to show
[P], and change [Q] to [Q'] as long as [Q] is enough to show
[Q'].
This observation is captured by the following _Rule of
Consequence_.
[[[
{{P'}} c {{Q'}}
P implies P' (in every state)
Q' implies Q (in every state)
-----------------------------
{{P}} c {{Q}}
]]]
For convenience, here are two more consequence rules -- one
for situations where we want to just strengthen the
precondition, and one for when we want to just loosen the
postcondition.
[[[
{{P'}} c {{Q}}
P implies P' (in every state)
-----------------------------
{{P}} c {{Q}}
{{P}} c {{Q'}}
Q' implies Q (in every state)
-----------------------------
{{P}} c {{Q}}
]]]
*)
*)
theorem hoare_consequence : "{{P'}} c {{Q'}} \<Longrightarrow> (\<forall> st. P st \<longrightarrow> P' st)
\<Longrightarrow> (\<forall> st. Q' st \<longrightarrow> Q st)
\<Longrightarrow> {{P}} c {{Q}}"
by (auto simp: hoare_triple_def)
theorem "\<lbrakk>{{P'}} c {{Q'}}; (\<And> st. P st \<Longrightarrow> P' st); (\<And> st. Q' st \<Longrightarrow> Q st)\<rbrakk>
\<Longrightarrow> {{P}} c {{Q}}"
unfolding hoare_triple_def
by simp
(*
Theorem hoare_consequence : forall (P P' Q Q' : Assertion) c,
{{P'}} c {{Q'}} ->
(forall st, P st -> P' st) ->
(forall st, Q' st -> Q st) ->
{{P}} c {{Q}}.
Proof.
unfold hoare_triple.
intros P P' Q Q' c Hht HPP' HQ'Q.
intros st st' Hc HP.
apply HQ'Q. apply (Hht st st'). assumption.
apply HPP'. assumption. Qed.
*)
theorem hoare_consequence_pre : "{{P'}} c {{Q}} \<Longrightarrow> (\<forall> st. P st \<longrightarrow> P' st)
\<Longrightarrow> {{P}} c {{Q}}"
by (auto intro: hoare_consequence)
(*
Theorem hoare_consequence_pre : forall (P P' Q : Assertion) c,
{{P'}} c {{Q}} ->
(forall st, P st -> P' st) ->
{{P}} c {{Q}}.
Proof.
intros P P' Q c Hhoare Himp.
apply hoare_consequence with (P' := P') (Q' := Q);
try assumption.
intros st H. apply H. Qed.
*)
theorem hoare_consequence_post : "{{P}} c {{Q'}} \<Longrightarrow> (\<forall> st. Q' st \<longrightarrow> Q st)
\<Longrightarrow> {{P}} c {{Q}}"
by (auto intro: hoare_consequence)
(*
Theorem hoare_consequence_post : forall (P Q Q' : Assertion) c,
{{P}} c {{Q'}} ->
(forall st, Q' st -> Q st) ->
{{P}} c {{Q}}.
Proof.
intros P Q Q' c Hhoare Himp.
apply hoare_consequence with (P' := P) (Q' := Q');
try assumption.
intros st H. apply H. Qed.
(** For example, we might use (the "[_pre]" version of) the
consequence rule like this:
[[
{{ True }} =>
{{ 1 = 1 }}
X ::= 1
{{ X = 1 }}
]]
Or, formally...
*)
Example hoare_asgn_example1 :
{{fun st => True}} (X ::= (ANum 1)) {{fun st => st X = 1}}.
Proof.
apply hoare_consequence_pre
with (P' := (fun st => 1 = 1)).
apply hoare_asgn_eq. reflexivity.
intros st H. reflexivity.
Qed.
*)
lemma "{{\<lambda> st. True}} (X ::= (ANum' 1)) {{\<lambda> st. st X = 1}}"
apply (rule hoare_consequence_pre [of "\<lambda> st. (1 :: nat) = 1"])
by (auto intro: hoare_asgn_eq simp: assn_sub_def)
lemma "{{\<lambda> st. True}} (X ::= (ANum' 1)) {{\<lambda> st. st X = 1}}"
apply (rule hoare_consequence_pre [of "\<lambda> st. (1 :: nat) = 1"])
apply (rule hoare_asgn_eq)
apply (simp add: assn_sub_def)
apply simp
done
(*
(* ####################################################### *)
(** *** Digression: The [eapply] Tactic *)
(** This is a good moment to introduce another convenient feature
of Coq. Having to write [P'] explicitly in the example above
is a bit annoying because the very next thing we are going to
do -- applying the [hoare_asgn] rule -- is going to determine
exactly what it should be. We can use [eapply] instead of
[apply] to tell Coq, essentially, "The missing part is going
to be filled in later." *)
Example hoare_asgn_example1' :
{{fun st => True}} (X ::= (ANum 1)) {{fun st => st X = 1}}.
Proof.
eapply hoare_consequence_pre.
apply hoare_asgn.
intros st H. reflexivity. Qed.
*)
(* CH: In general, applications of rule & drule can have free quantified variables that
they will introduce. These operate somewhat like the free variables introduced by eapply
Isabelle, by default, acts more like eapply than apply
*)
(*
(** In general, [eapply H] tactic works just like [apply H]
except that, instead of failing if unifying the goal with the
conclusion of [H] does not determine how to instantiate all
of the variables appearing in the premises of [H], [eapply H]
will replace these variables with _existential variables_
(written [?nnn]) as placeholders for expressions that will be
determined (by further unification) later in the proof.
There is also an [eassumption] tactic that works similarly. *)
(* ####################################################### *)
(** *** Skip *)
(** Since [SKIP] doesn't change the state, it preserves any
property P:
[[[
--------------------
{{ P }} SKIP {{ P }}
]]]
*)
Theorem hoare_skip : forall P,
{{P}} SKIP {{P}}.
Proof.
unfold hoare_triple. intros P st st' H HP. inversion H. subst.
assumption. Qed.
*)
(* CH: TODO - put the following theorem in Imp.thy as a default simp rule! *)
theorem skip_eq [simp]: "ceval SKIP st st' \<Longrightarrow> st = st'"
by (erule ceval.cases, auto)
theorem hoare_skip : "{{P}} SKIP {{P}}"
unfolding hoare_triple_def
apply (intro allI impI)
apply (drule skip_eq)
by simp
(* CH: Find out why I had to do the two applies of auto instead of forcing
st = st' by skip_eq right away *)
(*
(* ####################################################### *)
(** *** Sequencing *)
(** More interestingly, if the command [c1] takes any state where
[P] holds to a state where [Q] holds, and if [c2] takes any
state where [Q] holds to one where [R] holds, then doing [c1]
followed by [c2] will take any state where [P] holds to one
where [R] holds:
[[[
{{ P }} c1 {{ Q }}
{{ Q }} c2 {{ R }}
---------------------
{{ P }} c1;c2 {{ R }}
]]]
*)
Theorem hoare_seq : forall P Q R c1 c2,
{{Q}} c2 {{R}} ->
{{P}} c1 {{Q}} ->
{{P}} c1;c2 {{R}}.
Proof.
unfold hoare_triple.
intros P Q R c1 c2 H1 H2 st st' H12 Pre.
inversion H12; subst.
apply (H1 st'0 st'); try assumption.
apply (H2 st st'0); try assumption. Qed.
*)
theorem hoare_seq : "\<lbrakk>{{Q}} c2 {{R}};{{P}} c1 {{Q}}\<rbrakk> \<Longrightarrow> {{P}} (c1 ;; c2) {{R}}"
apply (auto simp: hoare_triple_def intro: ceval.intros)
apply (erule ceval.cases)
by auto
(*
(** Note that, in the formal rule [hoare_seq], the premises are
given in "backwards" order ([c2] before [c1]). This matches
the natural flow of information in many of the situations
where we'll use the rule. *)
(** Informally, a nice way of recording a proof using this rule
is as a "decorated program" where the intermediate assertion
[Q] is written between [c1] and [c2]:
[[
{{ a = n }}
X ::= a;
{{ X = n }} <---- Q
SKIP
{{ X = n }}
]]
*)
Example hoare_asgn_example3 : forall a n,
{{fun st => aeval st a = n}}
(X ::= a; SKIP)
{{fun st => st X = n}}.
Proof.
intros a n. eapply hoare_seq.
Case "right part of seq".
apply hoare_skip.
Case "left part of seq".
eapply hoare_consequence_pre. apply hoare_asgn.
intros st H. subst. reflexivity. Qed.
(** **** Exercise: 2 stars (hoare_asgn_example4) *)
(** Translate this decorated program into a formal proof:
[[
{{ True }} =>
{{ 1 = 1 }}
X ::= 1;
{{ X = 1 }} =>
{{ X = 1 /\ 2 = 2 }}
Y ::= 2
{{ X = 1 /\ Y = 2 }}
]]
*)
*)
lemma "{{\<lambda> st. True}} (X ::= (ANum' 1) ;; Y ::= (ANum' 2))
{{\<lambda> st. (st X =1) \<and> (st Y = 2)}}"
apply (rule hoare_seq [of "\<lambda> st. st X = 1"])
apply (rule hoare_consequence_pre [of "\<lambda> st. (st X = 1) \<and> ((2 :: nat) = 2)"])
apply (rule hoare_asgn_eq)
apply (simp add: assn_sub_def)
apply simp
apply (rule hoare_consequence_pre [of "\<lambda> st. (1::nat)=1"])
apply (rule hoare_asgn_eq)
apply (simp add: assn_sub_def)
apply simp
done
(*
Example hoare_asgn_example4 :
{{fun st => True}} (X ::= (ANum 1); Y ::= (ANum 2))
{{fun st => st X = 1 /\ st Y = 2}}.
Proof.
(* SOLUTION: *)
apply hoare_seq with (Q := fun st => st X = 1).
SCase "right part of seq".
eapply hoare_consequence_pre. apply hoare_asgn.
intros st H.
split.
rewrite update_neq; auto.
apply update_eq.
SCase "left part of seq".
eapply hoare_consequence_pre. apply hoare_asgn.
intros st H. unfold assn_sub. apply update_eq. Qed.
(** [] *)
(** **** Exercise: 3 stars, optional (swap_exercise) *)
(** Write an IMP program [c] that swaps the values of [X] and [Y]
and show (in Coq) that it satisfies the following
specification:
[[
{{X <= Y}} c {{Y <= X}}
]]
*)
*)
(*
(* SOLUTION: *)
Example swap_exercise :
{{fun st => st X <= st Y}}
(Z ::= (AId X); X ::= (AId Y); Y ::= (AId Z))
{{fun st => st Y <= st X}}.
Proof.
eapply hoare_seq.
eapply hoare_seq.
apply hoare_asgn.
apply hoare_asgn.
eapply hoare_consequence_pre.
apply hoare_asgn.
unfold assn_sub, update. simpl.
intros st H. assumption. Qed.
(** [] *)
(** **** Exercise: 3 stars, optional (hoarestate1) *)
(** Explain why the following proposition can't be proven:
[[
forall (a : aexp) (n : nat),
{{fun st => aeval st a = n}} (X ::= (ANum 3); Y ::= a)
{{fun st => st Y = n}}.
]]
*)
(* SOLUTION: *)
(* The problem is that [X] may occur inside (i.e. be read inside)
the expression [a]. If this is the case, and if location [X]
does not contain 3 in the state where the precondition is
evaluated, then [a] will evaluate to a value other than [n]
when it is assigned to [Y]. *)
(** [] *)
(* ####################################################### *)
(** *** Conditionals *)
(** What sort of rule do we want for reasoning about conditional
commands? Certainly, if the same assertion [Q] holds after
executing either branch, then it holds after the whole
conditional. So we might be tempted to write:
[[[
{{P}} c1 {{Q}}
{{P}} c2 {{Q}}
--------------------------------
{{P}} IFB b THEN c1 ELSE c2 {{Q}}
]]]
However, this is rather weak. For example, using this rule,
we cannot show that:
[[
{{True}}
IFB X == 0
THEN Y ::= 2
ELSE Y ::= X + 1
FI
{{ X <= Y }}
]]
since the rule tells us nothing about the state in which the
assignments take place in the then- and else- branches.
But, actually, we can say something more precise. In the
"then" branch, we know that the boolean expression [b]
evaluates to [true], and in the "else" branch, we know it
evaluates to [false]. Making this information available in
the premises of the lemma gives us more information to work
with when reasoning about the behavior of [c1] and [c2] (i.e.,
the reasons why they establish the postcondtion [Q]).
[[[
{{P /\ b}} c1 {{Q}}
{{P /\ ~b}} c2 {{Q}}
------------------------------------
{{P}} IFB b THEN c1 ELSE c2 FI {{Q}}
]]]
*)
(** To interpret this rule formally, we need to do a little work.
Strictly speaking, what we've written -- [P /\ b] -- is the
conjunction of an assertion and a boolean expression, which
doesn't typecheck. To fix this, we need a way of formally
"lifting" any bexp [b] to an assertion. We'll write [bassn
b] for the assertion "[b] evaluates to [true] in (a given
state)." *)
Definition bassn b : Assertion :=
fun st => beval st b = true.
(** A couple of useful facts about [bassn]: *)
Lemma bexp_eval_true : forall b st,
beval st b = true -> (bassn b) st.
Proof.
intros b st Hbe.
unfold bassn. assumption. Qed.
Lemma bexp_eval_false : forall b st,
beval st b = false -> ~ ((bassn b) st).
Proof.
intros b st Hbe contra.
unfold bassn in contra.
rewrite -> contra in Hbe. inversion Hbe. Qed.
(** Now we can formalize the Hoare proof rule for conditionals
(and prove it correct). *)
Theorem hoare_if : forall P Q b c1 c2,
{{fun st => P st /\ bassn b st}} c1 {{Q}} ->
{{fun st => P st /\ ~(bassn b st)}} c2 {{Q}} ->
{{P}} (IFB b THEN c1 ELSE c2 FI) {{Q}}.
Proof.
unfold hoare_triple.
intros P Q b c1 c2 HTrue HFalse st st' HE HP.
inversion HE; subst.
Case "b is true".
apply (HTrue st st').
assumption.
split. assumption.
apply bexp_eval_true. assumption.