2008
DOI: 10.1007/978-3-540-89439-1_24
|View full text |Cite
|
Sign up to set email alerts
|

Valigator: A Verification Tool with Bound and Invariant Generation

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
15
0

Year Published

2009
2009
2017
2017

Publication Types

Select...
5
2
1

Relationship

2
6

Authors

Journals

citations
Cited by 18 publications
(15 citation statements)
references
References 14 publications
0
15
0
Order By: Relevance
“…Similarly, the Why3 [18] verification platform generates VCs for C, Java, and Ada programs by converting them to an intermediate specification and programming language (WhyML). Similarly to Boogie, the Valigator tool [31] is able to infer loop invariants, but it uses different techniques (symbolic summation, Gröbner basis computation, and quantifier elimination) and the strongest postcondition calculus. The approach we have presented in this paper is able, like Boogie and Valigator, to automatically infer loop invariants.…”
Section: Related Work and Conclusionmentioning
confidence: 99%
“…Similarly, the Why3 [18] verification platform generates VCs for C, Java, and Ada programs by converting them to an intermediate specification and programming language (WhyML). Similarly to Boogie, the Valigator tool [31] is able to infer loop invariants, but it uses different techniques (symbolic summation, Gröbner basis computation, and quantifier elimination) and the strongest postcondition calculus. The approach we have presented in this paper is able, like Boogie and Valigator, to automatically infer loop invariants.…”
Section: Related Work and Conclusionmentioning
confidence: 99%
“…For example, these formulas can express the values of loop variables in terms of the loop counter, monotonicity properties of these variables considered as functions of the loop counter and polynomial relations among these variables. For extracting this information we deploy techniques from symbolic computation, such as recurrence solving and quantifier elimination, as presented in [3], [1], to perform inductive reasoning over scalar variables. (2) Using the derived loop properties, we then automatically discover first-order properties of the so-called update predicates for array variables used in the loop and monotonicity properties for scalar variables.…”
Section: Extended Abstractmentioning
confidence: 99%
“…Our method has thus advantage in automation, but it is restricted to ABC-loops. The approach presented in [11] infers invariants and bound assertions for loops with nested conditionals and assignments, where the assignments statements describe non-trivial recurrence relations over program variables (i.e. variable initializations are not allowed).…”
Section: Introductionmentioning
confidence: 99%
“…Bounds on iteration counters can be finally inferred if the iteration counters are changed by each path in the same manner. Due to these restrictions, nested loops cannot be handled in [11]. Contrarily to [11], we infer bound assertions as z-relations for nested loops, but, unlike [11], our invariant assertions are only over loop iteration variables and not arbitrary program variables.…”
Section: Introductionmentioning
confidence: 99%