- 06 Oct, 2015 1 commit
-
-
David Hauzar authored
-
- 30 Sep, 2015 1 commit
-
-
David Hauzar authored
Since the exact line of the construct that triggers VC may not be known, the possibility to map the counterexample information related to this construct to dedicated index instead of mapping it to line number was added. Note that the line of the construct that triggers VC is guaranteed to be known only if this construct does not span to multiple lines or if the VC is not split.
-
- 22 Sep, 2015 1 commit
-
-
David Hauzar authored
-
- 21 Sep, 2015 1 commit
-
-
David Hauzar authored
Model elements in source code line are represented as list of JSON objects with attributes "name", "value", and "kind". The attribute "name" is a name of a counterexample element, the attribute "value" is the value of the counterexample element, and the attribute "kind" is the kind of counterexample element, currently one of "old", "result", "error_message", and "other".
-
- 09 Sep, 2015 1 commit
-
-
MARCHE Claude authored
-
- 08 Sep, 2015 2 commits
-
-
David Hauzar authored
-
David Hauzar authored
-
- 07 Sep, 2015 1 commit
-
-
David Hauzar authored
-
- 04 Sep, 2015 2 commits
-
-
MARCHE Claude authored
-
David Hauzar authored
-
- 03 Sep, 2015 4 commits
-
-
David Hauzar authored
were added to original labels.
-
David Hauzar authored
When eval_match creates new terms from original terms, all labels of the original terms are copied to the new terms. The exception are labels of the form "model_trace:*". These labels are not copied if both original terms and new terms contain this label.
-
David Hauzar authored
In wp, eval_match is used to replace record fields with simple variables of the same type. Originally, all labels from the variable that field was accessed were copied to new variables representing fields of this variable. Therefore also "model_trace:var_name" label was copied and thus the field had name "var_name" in the counterexample. This commit solves this problem by appending names of the fields to "model_trace:*" label of new variables representing record fields.
-
MARCHE Claude authored
Incidentally, Try Why3 is now able to produce Alt-Ergo goals
-
- 01 Sep, 2015 2 commits
-
-
David Hauzar authored
-
David Hauzar authored
-
- 28 Aug, 2015 1 commit
-
-
David Hauzar authored
Parsing bitvectors in the counterexample returned by the prover.
-
- 11 Aug, 2015 1 commit
-
-
David Hauzar authored
-
- 06 Aug, 2015 1 commit
-
-
David Hauzar authored
Transformation intro_projections_counterexmp support more projections for a single type Ty.ty. The projections can have a name and this name is appended to the name of the function symbol or predicate being projected. This is useful for records - for record type, there can be a projection for each element of the type and the name of the projection can be the name of the element.
-
- 31 Jul, 2015 1 commit
-
-
David Hauzar authored
counterexample was got.
-
- 30 Jul, 2015 2 commits
-
-
David Hauzar authored
the counter-example is empty while printing part of the counter-example related to the term that triggers VC.
-
David Hauzar authored
triggering VC was not collected.
-
- 27 Jul, 2015 1 commit
-
-
David Hauzar authored
construct that triggers VC in Smtv2.info instead of global variable.
-
- 24 Jul, 2015 1 commit
-
-
David Hauzar authored
that triggers VC.
-
- 22 Jul, 2015 2 commits
-
-
David Hauzar authored
triggers VC in Model_parser.model and printing them.
-
David Hauzar authored
in counter-example.
-
- 18 Jul, 2015 1 commit
-
-
MARCHE Claude authored
-
- 17 Jul, 2015 1 commit
-
-
MARCHE Claude authored
-
- 16 Jul, 2015 5 commits
-
-
David Hauzar authored
-
David Hauzar authored
-
David Hauzar authored
to the counter-example model. This line must be marked with the label "model_vc". If VC line is postcondition, it can be marked with the label "model_func" or "model_func:func_name". Terms corresponding to old values of arguments will be marked with @old, term corresponding to the function result will be marked with @result or func_name@result if func_name was given. Pretty printing of model element names in counter-example. Possibility to print differently model elements corresponding to function result, old values of function arguments and other model elements.
-
Martin Clochard authored
This commit enable the possibility to change discriminate behavior from Why3 source files. The 4 metas that configure the transformation: select_inst select_lsinst select_lskept select_kept can now be configured from source files (actually they could before, but their value was overriden by the drivers). The behavior in absence of annotation can be specified from drivers using the 4 new configuration metas: select_inst_default select_lsinst_default select_lskept_default select_kept_default They behave as their non-default counterparts, except they have lower precedence. This avoid the forementioned overriding problem.
-
MARCHE Claude authored
-
- 15 Jul, 2015 3 commits
-
-
David Hauzar authored
-
David Hauzar authored
-
David Hauzar authored
Conflicts: src/core/model_parser.ml
-
- 10 Jul, 2015 1 commit
-
-
MARCHE Claude authored
-
- 07 Jul, 2015 1 commit
-
-
MARCHE Claude authored
-
- 21 Jun, 2015 1 commit
-
-
Andrei Paskevich authored
-
- 09 Jun, 2015 1 commit
-
-
David Hauzar authored
-