2014
DOI: 10.1007/s10009-014-0314-5
|View full text |Cite
|
Sign up to set email alerts
|

Let’s verify this with Why3

Abstract: We present solutions to the three challenges of the VerifyThis competition held at the 18th FM symposium in August 2012. These solutions use the Why3 environment for deductive program verification.

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
42
0
2

Year Published

2015
2015
2020
2020

Publication Types

Select...
7
3

Relationship

5
5

Authors

Journals

citations
Cited by 48 publications
(47 citation statements)
references
References 13 publications
0
42
0
2
Order By: Relevance
“…Verification of complex code with Why3 and automatic provers typically expects user guidance through addition of intermediate assertions [19] and verification-only code (ghost code) [11]. See Why3's Web site 6 for an extensive tutorial and a large collection of examples [6].…”
Section: From Whyml To Cmentioning
confidence: 99%
“…Verification of complex code with Why3 and automatic provers typically expects user guidance through addition of intermediate assertions [19] and verification-only code (ghost code) [11]. See Why3's Web site 6 for an extensive tutorial and a large collection of examples [6].…”
Section: From Whyml To Cmentioning
confidence: 99%
“…We based our prototype implementation on the Why3 platform [4]. Why3 offers an expressive formalization language, an efficient Weakest-Precondition (WP) calculus [5] implementation and a rich API to send the obtained verification conditions to several automated solvers.…”
Section: Introductionmentioning
confidence: 99%
“…The goal is to provide simplified interactions between the user and the failing VC, so as to investigate a proof task without the need to rely on an external interactive prover. A specificity of SPARK is that the underlying toolchain from the given input Ada program to the VCs makes use of the external intermediate language Why3 [6] that itself provides access to many different automated provers (mainly Alt-Ergo, CVC4 and Z3) but also general purpose interactive theorem provers (Coq, Isabelle/HOL, PVS). Indeed, an extreme mean to investigate a proof failure is to launch an interactive theorem prover on the failing VC and to start writing a manual proof.…”
Section: Introductionmentioning
confidence: 99%