6. Reference Manuals for the Why3 Tools

This chapter details the usage of each of the command-line tools provided by the Why3 environment. The main command is why3; it acts as an entry-point to all the features of Why3. It is invoked as follows:

why3 [general options...] <command> [specific options...]

The following commands are available:

config

Manage the user’s configuration, including the detection of installed provers.

doc

Render a WhyML file as HTML.

execute

Perform a symbolic execution of a WhyML file.

extract

Generate an OCaml program corresponding to a WhyML file.

ide

Provide a graphical interface to display goals and to run provers and transformations on them.

pp

Pretty-print WhyML definitions (formatting .mlw files or printing inductive definitions to LaTeX).

prove

Read a WhyML input file and call provers, on the command-line.

realize

Generate the skeleton of an interactive proof for a WhyML file.

replay

Replay the proofs stored in a session, for regression test purposes.

session

Dump various informations from a proof session, and possibly modifies the session.

wc

Give some token statistics about a WhyML file.

All these commands are also available as standalone executable files, if needed.

The commands accept a common subset of command-line options. In particular, option --help displays the usage and options.

-L <dir>, --library=<dir>

Add <dir> in the load path, to search for theories.

-C <file>, --config=<file>

Read the configuration from the given file. See Section 12.3.

--extra-config=<file>

Read additional configuration from the given file. See Section 12.3.

--list-debug-flags

List known debug flags.

--list-transforms

List known transformations.

--list-printers

List known printers.

--list-provers

List known provers.

--list-formats

List known input formats.

--list-metas

List known metas. See also Section 12.9 for a description of some of those metas.

--debug-all

Set all debug flags (except flags that change the behavior).

--debug=<flag>,...

Set some specific debug flags. See also Section 12.10 for a description of some of those flags.

--help

Display the usage and the exact list of options for the given tool.

WHY3CONFIG

Indicate where to find the why3.conf file. Can be overwritten using the --config option.

6.1. The config Command

Why3 must be configured to access external provers. Typically, this is done by running why3 config detect. This command must be run every time a new prover is installed.

The provers known by Why3 are described in the configuration file provers-detection-data.conf of the Why3 data directory (e.g., /usr/local/share/why3). Advanced users may try to modify this file to add support for detection of other provers. (In that case, please consider submitting a new prover configuration on the bug tracking system.)

The result of prover detection is stored in the user’s configuration file (see Section 12.3). Only the version of the provers is stored; the actual configuration of the provers, shortcuts, strategies, and editors, are regenerated at each startup of a Why3. This configuration can be inspected with the command why3 config show.

If a supported prover is not automatically recognized by why3 config detect, the command why3 config add-prover can be used to add it.

The available subcommands are as follows:

config add-prover

Manually register a prover.

config detect

Automatically detect installed provers.

config list-supported-provers

List the names of all supported provers.

config show

Show the expanded version of the configuration file.

Only the first two commands modify the configuration file.

6.1.1. Command add-prover

This commands adds a prover to the configuration. It is invoked as follows.

why3 config add-prover <name> <file> [<shortcut>]

Argument name is the name of the prover, as listed by command why3 config list-supported-provers and as found in file provers-detection-data.conf.

If the argument shortcut is present, it is used as the shortcut for invoking the prover.

For example, to add an Alt-Ergo executable /home/me/bin/alt-ergo-trunk with shortcut new-ae, one can type

why3 config add-prover Alt-Ergo /home/me/bin/alt-ergo-trunk new-ae

Manually added provers are stored in the configuration file under [manual_binary] sections as well as [detected_binary] ones.

6.1.2. Command detect

This command automatically detects the installed provers that are supported by Why3. It also creates a configuration file if none exists.

Automatically detected provers are stored in the configuration file under [detected_binary] sections.

6.1.3. Command list-supported-provers

This command lists the names of all supported provers, as used for command why3 config add-prover.

6.1.4. Command show

This command shows the expanded version of the configuration file.

6.2. The prove Command

Why3 is primarily used to call provers on goals contained in an input file. By default, such a file must be written in WhyML language (extension .mlw). However, a dynamically loaded plugin can register a parser for some other format of logical problems, e.g., TPTP or SMT-LIB.

The prove command executes the following steps:

  1. Parse the command line and report errors if needed.

  2. Read the configuration file using the priority defined in Section 12.3.

  3. Load the plugins mentioned in the configuration. It will not stop if some plugin fails to load.

  4. Parse and typecheck the given files using the correct parser in order to obtain a set of Why3 theories for each file. It uses the filename extension or the --format option to choose among the available parsers. why3 --list-formats lists the registered parsers. WhyML modules are turned into theories containing verification conditions as goals.

  5. Extract the selected goals inside each of the selected theories into tasks. The goals and theories are selected using options --goal and --theory. Option --theory applies to the previous file appearing on the command line. Option --goal applies to the previous theory appearing on the command line. If no theories are selected in a file, then every theory is considered as selected. If no goals are selected in a theory, then every goal is considered as selected.

  6. Apply the transformations requested with --apply-transform in their order of appearance on the command line. why3 --list-transforms lists the known transformations; plugins can add more of them.

  7. Apply the driver selected with the --driver option, or the driver of the prover selected with the --prover option. why3 --list-provers lists the known provers, the ones that appear in the configuration file.

  8. If option --prover is given, call the selected prover on each generated task and print the results. If option --driver is given, print each generated task using the format specified in the selected driver.

  9. Derive a validated counterexample using runtime-assertion checking, if option --check-ce is given and the selected prover generated a counterexample, .

6.2.1. Prover Results

The provers can give the following output:

Valid

The goal is proved in the given context.

Unknown

The prover has stopped its search.

Timeout

The prover has reached the time limit.

Failure

An error has occurred.

Invalid

The prover knows the goal cannot be proved.

6.2.2. Options

-F <format>, --format=<format>

Select the given input format.

-T <theory>, --theory=<theory>

Focus on the given theory. If the argument is not qualified, the theory is searched in the input file.

-G <goal>, --goal=<goal>

Focus on the given goal. The goal is searched in the theory given by --theory, if any. Otherwise, it is searched in the toplevel namespace of the input file.

-a <transform>, --apply-transform=<transform>

Apply the given transformation to the goals.

-P <prover>, --prover=<prover>

Execute the given prover on the goals.

-D <driver>, --driver=<driver>

Output the tasks obtained by applying the given driver to the goals. This option conflicts with --prover.

--extra-expl-prefix=<s>

Specify s as an additional prefix for labels that denotes VC explanations. The option can be used several times to specify several prefixes.

--check-ce

Validate the counterexample using runtime-assertion checking. Only applicable when the prover selected by --prover is configured to generate a counterexample.

--rac-prover=<p>

Use prover p for the runtime-assertion checking during the validation of counterexamples, when term reduction is insufficient (which is always tried first). The prover p is the name or shortcut of a prover, with optional, comma-separated time limit and memory limit, e.g. cvc4,2,1000.

--rac-try-negate

Try to decide the validity of an assertion by negating the assertion and the prover answer (if any), when a prover is defined for RAC using --rac-prover but unable to decide the validity of the un-negated assertion.

6.2.3. Generating potential counterexamples

When the selected prover has alternative counterexample, the prover is instructed to generate a model, and Why3 elaborates the model into a potential counterexample. The potential counterexample associates source locations and variables to values. The generation and display of potential counterexamples is presented in details in Section 6.3.7.

6.2.4. Generating validated counterexamples

A validated counterexample can be requested using option --check-ce. The validated counterexample is derived by executing the relevant function using runtime assertion checking (RAC) 1. The potential counterexample serves as an oracle for values that are not or cannot be computed in the RAC execution (e.g., arguments to the relevant function or any-expressions).

The validated counterexample is a trace of the RAC execution, with one of the following qualifications:

The program does not comply to the verification goal:

The validated counterexample is the trace of an execution that resulted in the violation of an assertion.

The contracts of some function or loop are underspecified:

The validated counterexample is the trace of an abstract execution, which resulted in the violation of an assertion. In an abstract execution, function calls and loops are not executed. Their results and assignments are instead chosen according to the contracts (function postcondition or loop invariants) by picking them from the potential counterexample.

The program does not comply to the verification goal, or the contracts of some loop or function are too weak:

Either of the above cases.

Sorry, we don’t have a good counterexample for you :(

The RAC execution did not violate any assertions. The execution trace does not constitute a validated counterexample, and the potential counterexample is invalid, so no counterexample is shown.

The counterexample model could not be verified:

The validated counterexample could not be derived because RAC execution was incomplete. The potential counterexample is instead shown with a warning.

1

The relevant function is generally only defined, when the counterexample is not generated for the VC of the complete program, for example by applying a split transformation using --apply-transform=split_vc.

6.3. The ide Command

The basic usage of the GUI is described by the tutorial of Section 2.2. The command-line options are the common options detailed in introduction to this chapter, plus the specific option already described for the prove command in Section 6.2.2.

At least one anonymous argument must be specified on the command line. More precisely, the first anonymous argument must be the directory of the session. If the directory does not exist, it is created. The other arguments should be existing files that are going to be added to the session. For convenience, if there is only one anonymous argument, it can be an existing file and in this case the session directory is obtained by removing the extension from the file name.

6.3.1. Session

The session stores the transformations you performed on each verification condition, as well as the provers you ran. Such a proof attempt records the complete name of a prover (name, version, optional attribute), the time limit and memory limit given, and the result of the prover. The result of the prover is the same as when you run the prove command. It contains the time taken and the state of the proof:

Valid

The task is valid according to the prover. The goal is considered proved.

Invalid

The task is invalid.

Timeout

the prover exceeded the time limit.

OufOfMemory

The prover exceeded the memory limit.

Unknown

The prover cannot determine if the task is valid. Some additional information can be provided.

Failure

The prover reported a failure.

HighFailure

An error occurred while trying to call the prover, or the prover answer was not understood.

Additionally, a proof attempt can have the following attributes:

obsolete

The prover associated to that proof attempt has not been run on the current task, but on an earlier version of that task. You need to replay the proof attempt, run the prover with the current task of the proof attempt, in order to update the answer of the prover and remove this attribute.

detached

The proof attempt is not associated to a proof task anymore. The reason might be that a proof goal disappeared, or that there is a syntax or typing error in the current file, that makes all nodes temporarily detached until the parsing error is fixed. Detached nodes of the session tree are kept until they are explicitly removed, either using a remove command or the clean command. They can be reused, as any other nodes, using the copy/paste operation.

Generally, proof attempts are marked obsolete just after the start of the user interface. Indeed, when you load a session in order to modify it (not with why3 session info for instance), Why3 rebuilds the goals to prove by using the information provided in the session. If you modify the original file (.mlw) or if the transformations have changed (new version of Why3), Why3 will detect that. Since the provers might answer differently on these new proof obligations, the corresponding proof attempts are marked obsolete.

6.3.2. Context Menu

The left toolbar that was present in former versions of Why3 is now replaced by a context menu activited by clicking the right mouse button, while cursor is on a given row of the proof session tree.

Prover list

List the detected provers. Note that you can hide some provers of that list using File ‣ Preferences, tab Provers.

Strategy list

List the set of known strategies.

Edit

Start an editor on the selected task.

Replay valid obsolete proofs

All proof nodes below the selected nodes that are obsolete but whose former status was Valid are replayed.

Replay all obsolete proofs

All proof nodes below the selected nodes that are obsolete are replayed.

Clean node

Remove any unsuccessful proof attempt for which there is another successful proof attempt for the same goal.

Remove node

Remove a proof attempt or a transformation.

Interrupt

Cancel all the proof attempts currently scheduled or running.

6.3.4. Command-line interface

Between the top-right zone containing source files and task, and the bottom-right zone containing various messages, a text input field allows the user to invoke commands using a textual interface (see Fig. 2.1). The help command displays a basic list of available commands. All commands available in the menus are also available as a textual command. However the textual interface allows for much more possibilities, including the ability to invoke transformations with arguments.

6.3.5. Key shortcuts

  • Save session and files: Control-s

  • Save all and refresh session: Control-r

  • Quit: Control-q

  • Enlarge font: Control-plus

  • Reduce font: Control-minus

  • Collapse proved goals: !

  • Collapse current node: -

  • Expand current node: +

  • Copy: Control-c

  • Paste: Control-v

  • Select parent node: Control-up

  • Select next unproven goal: Control-down

  • Change focus to command line: Return

  • Edit: e

  • Replay: r

  • Clean: c

  • Remove: Delete

  • Mark obsolete : o

6.3.6. Preferences Dialog

The preferences dialog allows you to customize various settings. They are grouped together under several tabs.

Note that there are to different buttons to close that dialog. The Close button will make modifications of any of these settings effective only for the current run of the GUI. The SaveClose button will save the modified settings in Why3 configuration file, to make them permanent.

Tab General

allows one to set various general settings.

  • the limits set on resource usages:

    • the time limit given to provers, in seconds

    • the memory given to provers, in megabytes

    • the maximal number of simultaneous provers allowed to run in parallel

  • option to disallow source editing within the GUI

  • the policy for saving sessions:

    • always save on exit (default): the current state of the proof session is saving on exit

    • never save on exit: the current state of the session is never saved automatically, you must use menu File ‣ Save session

    • ask whether to save: on exit, a popup window asks whether you want to save or not.

Tab Appearance
  • show full task context: by default, only the local context of formulas is shown, that is only the declarations comming from the same module

  • show attributes in formulas

  • show coercions in formulas

  • show source locations in formulas

  • show time and memory limits for each proof

Finally, it is possible to choose an alternative icon set, provided, one is installed first.

Tab Editors

allows one to customize the use of external editors for proof scripts.

  • The default editor to use when the button is pressed.

  • For each installed prover, a specific editor can be selected to override the default. Typically if you install the Coq prover, then the editor to use will be set to “CoqIDE” by default, and this dialog allows you to select the Emacs editor and its Proof General mode instead.

Tab Provers

allows to select which of the installed provers one wants to see in the context menu.

Tab Uninstalled provers policies

presents all the decision previously taken for missing provers, as described in Section 5.2.2. You can remove any recorded decision by clicking on it.

6.3.7. Displaying Counterexamples

Why3 provides some support for extracting a potential counterexample from failing proof attempts, for provers that are able to produce a counter-model of the proof task. Why3 attempts to turn this counter-model into values for the free variables of the original Why3 input. Currently, this is supported for CVC4 prover version at least 1.5, and Z3 prover version at least 4.4.0.

The generation of counterexamples is fully integrated in Why3 IDE. The recommended usage is to first start a prover normally, as shown in Fig. 6.1) and then click on the status icon for the corresponding proof attempt in the tree. Alternatively, one can use the key shortcut G or type get-ce in the command entry. The result can be seen on Fig. 6.2: the same prover but with the alternative counterexamples is run. The resulting counterexample is displayed in two different ways. First, it is displayed in the Task tab of the top-right window, at the end of the text of the task, under the form of a list of pairs “variable = value”, ordered by the line number of the source code in which that variable takes that value. Second, it is displayed in the Counterexample tab of the bottom right window, this time interleaved with the code, as shown in Fig. 6.2.

Failing execution of CVC4

Fig. 6.1 Failing execution of CVC4

Counterexamples display for CVC4

Fig. 6.2 Counterexamples display for CVC4

6.3.7.1. Notes on format of displayed values

The counterexamples can contain values of various types.

  • Integer or real variables are displayed in decimal.

  • Bitvectors are displayed in hexadecimal.

  • Integer range types are displayed in a specific notation showing their projection to integers.

  • Floating-point numbers are displayed both under a decimal approximation and an exact hexadecimal value. The special values +oo, -oo, and NaN may occur too.

  • Values from algebraic types and record types are displayed as in the Why3 syntax.

  • Map values are displayed in a specific syntax detailed below.

To detail the display of map values, consider the following code with a trivially false postcondition:

use int.Int
use ref.Ref
use map.Map

let ghost test_map (ghost x : ref (map int int)) : unit
  ensures { !x[0] <> !x[1] }
=
  x := Map.set !x 0 3

Executing CVC4 with the “counterexamples” alternative on goal will trigger counterexamples:

use int.Int
use ref.Ref
use map.Map

let ghost test_map (ghost x : ref (map int int)) : unit
(* x = (1 => 3,others => 0) *)
  ensures { !x[0] <> !x[1] }
  (* x = (0 => 3,1 => 3,others => 0) *)
=
  x := Map.set !x 0 3
  (* x = (0 => 3,1 => 3,others => 0) *)

The notation for map is to be understood with indices on left of the arrows and values on the right “(index => value)”. The meaning of the keyword others is the value for all indices that were not mentioned yet. This shows that setting the parameter x to a map that has value 3 for index 1 and zero for all other indices is a counterexample. We can check that this negates the ensures clause.

6.3.7.2. Known limitations

The counterexamples are known not to work on the following non-exhaustive list (which is undergoing active development):

  • Code containing type polymorphism is often a problem due to the bad interaction between monomorphisation techniques and counterexamples. This is current an issue in particular for the Array module of the standard library.

More information on the implementation of counterexamples in Why3 can be found in [HMM16] and in [DHMM18]. For the producing counterexamples using the Why3 API, see Section 4.10.

6.4. The replay Command

The why3 replay command is meant to execute the proofs stored in a Why3 session file, as produced by the IDE. Its main purpose is to play non-regression tests. For instance, examples/regtests.sh is a script that runs regression tests on all the examples.

The tool is invoked in a terminal or a script using

why3 replay [options] <project directory>

The session file why3session.xml stored in the given directory is loaded and all the proofs it contains are rerun. Then, all the differences between the information stored in the session file and the new run are shown.

Nothing is shown when there is no change in the results, whether the considered goal is proved or not. When all the proof are done, a summary of what is proved or not is displayed using a tree-shape pretty print, similar to the IDE tree view after doing View ‣ Collapse proved goals. In other words, when a goal, a theory, or a file is fully proved, the subtree is not shown.

6.4.1. Obsolete proofs

When some proof attempts stored in the session file are obsolete, the replay is run anyway, as with the replay button in the IDE. Then, the session file will be updated if both

  • all the replayed proof attempts give the same result as what is stored in the session,

  • all the goals are proved.

In other cases, you can use the IDE to update the session, or use the option --force described below.

6.4.2. Exit code and options

The exit code is 0 if no difference was detected, 1 if there was. Other exit codes mean some failure in running the replay.

Options are:

-s

Suppress the output of the final tree view.

-q

Run quietly (no progress info).

--force

Enforce saving the session, if all proof attempts replayed correctly, even if some goals are not proved.

--obsolete-only

Replay the proofs only if the session contains obsolete proof attempts.

--smoke-detector[=none|top|deep]

Try to detect if the context is self-contradicting (default: top).

--prover=<prover>

Restrict the replay to the selected provers only.

6.4.3. Smoke detector

The smoke detector tries to detect if the context is self-contradicting and, thus, that anything can be proved in this context. The smoke detector can’t be run on an outdated session and does not modify the session. It has three possible configurations:

none

Do not run the smoke detector.

top

The negation of each proved goal is sent with the same timeout to the prover that proved the original goal.

Goal G : forall x:int. q x -> (p1 x \/ p2 x)

becomes

Goal G : ~ (forall x:int. q x -> (p1 x \/ p2 x))

In other words, if the smoke detector is triggered, it means that the context of the goal G is self-contradicting.

deep

This is the same technique as top but the negation is pushed under the universal quantification (without changing them) and under the implication. The previous example becomes

Goal G : forall x:int. q x /\ ~ (p1 x \/ p2 x)

In other words, the premises of goal G are pushed in the context, so that if the smoke detector is triggered, it means that the context of the goal G and its premises are self-contradicting. It should be clear that detecting smoke in that case does not necessarily means that there is a mistake: for example, this could occur in the WP of a program with an unfeasible path.

At the end of the replay, the name of the goals that triggered the smoke detector are printed:

goal 'G', prover 'Alt-Ergo 0.93.1': Smoke detected!!!

Moreover Smoke detected (exit code 1) is printed at the end if the smoke detector has been triggered, or No smoke detected (exit code 0) otherwise.

6.5. The session Command

The why3 session command makes it possible to extract information from proof sessions on the command line, or even modify them to some extent. The invocation of this program is done under the form

why3 session <subcommand> [options] <session directories>

The available subcommands are as follows:

session info

Print information and statistics about sessions.

session latex

Output session contents in LaTeX format.

session html

Output session contents in HTML format.

session update

Update session contents.

The first three commands do not modify the sessions, whereas the last modify them.

6.5.1. Command info

The why3 session info command reports various informations about the session, depending on the following specific options.

--provers

Print the provers that appear inside the session, one by line.

--edited-files

Print all the files that appear in the session as edited proofs.

--stats

Print various proofs statistics, as detailed below.

--print0

Separate the results of the options --provers and --edited-files by the null character \0 instead of end of line \n. That allows you to safely use (even if the filename contains space or carriage return) the result with other commands. For example you can count the number of proof line in all the coq edited files in a session with:

why3 session info --edited-files vstte12_bfs --print0 | xargs -0 coqwc

or you can add all the edited files in your favorite repository with:

why3 session info --edited-files --print0 vstte12_bfs.mlw | \
    xargs -0 git add

6.5.1.1. Session Statistics

The proof statistics given by option --stats are as follows:

  • Number of goals: give both the total number of goals, and the number of those that are proved (possibly after a transformation).

  • Goals not proved: list of goals of the session which are not proved by any prover, even after a transformation.

  • Goals proved by only one prover: the goals for which there is only one successful proof. For each of these, the prover which was successful is printed. This also includes the sub-goals generated by transformations.

  • Statistics per prover: for each of the prover used in the session, the number of proved goals is given. This also includes the sub-goals generated by transformations. The respective minimum, maximum and average time and on average running time is shown. Beware that these time data are computed on the goals where the prover was successful.

For example, here are the session statistics produced on the “hello proof” example of Section 2.

== Number of root goals ==
  total: 3  proved: 2

== Number of sub goals ==
  total: 2  proved: 1

== Goals not proved ==
  +-- file ../hello_proof.why
    +-- theory HelloProof
      +-- goal G2
        +-- transformation split_goal_right
          +-- goal G2.0

== Goals proved by only one prover ==
  +-- file ../hello_proof.why
    +-- theory HelloProof
      +-- goal G1: Alt-Ergo 0.99.1
      +-- goal G2
        +-- transformation split_goal_right
          +-- goal G2.1: Alt-Ergo 0.99.1
      +-- goal G3: Alt-Ergo 0.99.1

== Statistics per prover: number of proofs, time (minimum/maximum/average) in seconds ==
  Alt-Ergo 0.99.1     :   3   0.00   0.00   0.00

6.5.2. Command latex

The why3 session latex command produces a summary of the replay under the form of a tabular environment in LaTeX, one tabular for each theory, one per file.

The specific options are

--style=<n>

Set output style (1 or 2, default 1). Option --style=2 produces an alternate version of LaTeX output, with a different layout of the tables.

-o <dir>

Indicate where to produce LaTeX files (default: the session directory).

--longtable

Use the longtable environment instead of tabular.

-e <elem>

Produce a table for the given element, which is either a file, a theory or a root goal. The element must be specified using its path in dot notation, e.g., file.theory.goal. The file produced is named accordingly, e.g., file.theory.goal.tex. This option can be given several times to produce several tables in one run. When this option is given at least once, the default behavior that is to produce one table per theory is disabled.

6.5.2.1. Customizing LaTeX output

The generated LaTeX files contain some macros that must be defined externally. Various definitions can be given to them to customize the output.

\provername

macro with one parameter, a prover name.

\valid

macro with one parameter, used where the corresponding prover answers that the goal is valid. The parameter is the time in seconds.

\noresult

macro without parameter, used where no result exists for the corresponding prover.

\timeout

macro without parameter, used where the corresponding prover reached the time limit.

\explanation

macro with one parameter, the goal name or its explanation.

Here are some examples of macro definitions:

\usepackage{xcolor}
\usepackage{colortbl}
\usepackage{rotating}

\newcommand{\provername}[1]{\cellcolor{yellow!25}
\begin{sideways}\textbf{#1}~~\end{sideways}}
\newcommand{\explanation}[1]{\cellcolor{yellow!13}lemma \texttt{#1}}
\newcommand{\transformation}[1]{\cellcolor{yellow!13}transformation \texttt{#1}}
\newcommand{\subgoal}[2]{\cellcolor{yellow!13}subgoal #2}
\newcommand{\valid}[1]{\cellcolor{green!13}#1}
\newcommand{\unknown}[1]{\cellcolor{red!20}#1}
\newcommand{\invalid}[1]{\cellcolor{red!50}#1}
\newcommand{\timeout}[1]{\cellcolor{red!20}(#1)}
\newcommand{\outofmemory}[1]{\cellcolor{red!20}(#1)}
\newcommand{\noresult}{\multicolumn{1}{>{\columncolor[gray]{0.8}}c|}{~}}
\newcommand{\failure}{\cellcolor{red!20}failure}
\newcommand{\highfailure}{\cellcolor{red!50}FAILURE}

6.5.3. Command html

The why3 session html command produces a summary of the proof session in HTML syntax. There are two styles of output: table and simpletree. The default is table.

The file generated is named why3session.html and is written in the session directory by default (see option -o to override this default).

HTML table produced for the HelloProof example

Fig. 6.3 HTML table produced for the HelloProof example

The style table outputs the contents of the session as a table, similar to the LaTeX output above. Fig. 6.3 is the HTML table produced for the ‘HelloProof’ example, as typically shown in a Web browser. The gray cells filled with --- just mean that the prover was not run on the corresponding goal. Green background means the result was “Valid”, other cases are in orange background. The red background for a goal means that the goal was not proved.

The style simpletree displays the contents of the session under the form of tree, similar to the tree view in the IDE. It uses only basic HTML tags such as <ul> and <li>.

Specific options for this command are as follows.

--style=[simpletree|table]

Set the style to use, among simpletree and table (default: table).

-o <dir>

Set the directory where to output the produced files (- for stdout). The default is to output in the same directory as the session itself.

--context

Add context around the generated code in order to allow direct visualization (header, css, etc.). It also adds in the output directory all the needed external files. It is incompatible with stdout output.

--add_pp=<suffix>,<cmd>,<out_suffix>

Set a specific pretty-printer for files with the given suffix. Produced files use <out_suffix> as suffix. <cmd> must contain %i which will be replaced by the input file and %o which will be replaced by the output file.

--coqdoc

use the coqdoc command to display Coq proof scripts. This is equivalent to --add_pp=.v,coqdoc --no-index --html -o %o %i,.html

6.5.4. Command update

The why3 session update command permits to modify the session contents, depending on the following specific options.

--rename-file=<src>:<dst>

rename the file <src> to <dst> in the session. The file <src> itself is also renamed to <dst> in your filesystem.

6.6. The doc Command

The why3 doc command can produce HTML pages from Why3 source code. Why3 code for theories or modules is output in preformatted HTML code. Comments are interpreted in three different ways.

  • Comments starting with at least three stars are completed ignored.

  • Comments starting with two stars are interpreted as textual documentation. Special constructs are interpreted as described below. When the previous line is not empty, the comment is indented to the right, so as to be displayed as a description of that line.

  • Comments starting with one star only are interpreted as code comments, and are typeset as the code

Additionally, all the Why3 identifiers are typeset with links so that one can navigate through the HTML documentation, going from some identifier use to its definition.

6.6.1. Options

-o <dir>, --output=<dir>

Define the directory where to output the HTML files.

--index

Generate an index file index.html. This is the default behavior if more than one file is passed on the command line.

--no-index

Prevent the generation of an index file.

--title=<title>

Set title of the index page.

--stdlib-url=<url>

Set a URL for files found in load path, so that links to definitions can be added.

6.6.2. Typesetting textual comments

Some constructs are interpreted:

  • {c text} interprets character c as some typesetting command:

    1-6

    a heading of level 1 to 6 respectively

    h

    raw HTML

  • `code` is a code escape: the text code is typeset as Why3 code.

A CSS file style.css suitable for rendering is generated in the same directory as output files. This CSS style can be modified manually, since regenerating the HTML documentation will not overwrite an existing style.css file.

6.7. The pp Command

This tool pretty-prints Why3 declarations into various forms. The kind of output is specified using the --output option.

why3 pp [--output=mlw|sexp|latex|dep] [--kind=inductive] [--prefix=<prefix>] \
  <filename> <file>[[.<Module>].<ind_type>] ...
--output=<output>

Set the output format, among the following:

  • mlw: reformat WhyML source code.

  • sexp: print the abstract syntax tree of a WhyML file (data-type from API module Ptree) as a S-expression (enabled only when package ppx_sexp_conv is available at configuration time of Why3).

  • latex: currently can be used to print WhyML inductive definitions to LaTeX, using the mathpartir package.

  • dep: display module dependencies, under the form of a digraph using the dot syntax from the GraphViz visualisation software.

--kind=<kind>

Set the syntactic kind to be pretty printed. Currently, the only supported kind are inductive types (--kind=inductive) when using the LaTeX output (--output=latex).

--prefix=<prefix>

Set the prefix for LaTeX commands when using --output=latex. The default prefix is WHY.

For the LaTeX output, the typesetting of variables, record fields, and functions can be configured by LaTeX commands. Dummy definitions of these commands are printed in comments and have to be defined by the user. Trailing digits and quotes are removed from the command names to reduce the number of commands.

6.8. The execute Command

Why3 can execute expressions in the context of a WhyML program (extension .mlw).

why3 execute [options] <file> <expr>

file is a WhyML file, and expr is a WhyML expression. Using option --use=<M> the definitions from module M are added to the context for executing expr. For example, the following command executes Mod1.f 42 defined in myfile.mlw:

why3 execute myfile.mlw --use=Mod1 'f 42'

Upon completion of the execution, the value of the result is displayed on the standard input. Additionally, values of the global mutable variables modified by that function are displayed too.

See more details and examples of use in Section 10.1.

6.8.1. Runtime assertion checking (RAC)

The execution can be instructed using option --rac to check the validity of the program annotations that are encountered during the execution. This includes the validation of assertions, function contracts, and loop invariants 2.

There are two strategies to check the validity of an annotation: First, the term is reduced using the Why3 transformation compute_in_goal. The annotation is valid when the result of the reduction is true and invalid when the result is false. When the transformation cannot reduce the term to a trivial term, and when a RAC prover is given using option --rac-prover, the prover is used to verify the term.

When a program annotation is found to be wrong during the execution, the execution stops and reports the contradiction. Normally, the execution continues when an annotation cannot be checked (when the term can neither be reduced nor proven), but fails when option –rac-fail-cannot-check is given.

6.8.2. Options

--use=<Mod>

Add the definitions from Mod to the execution context.

--rac

Check the validity of program annotations encountered during the execution.

--rac-prover=<p>

Same option as for prove.

--rac-try-negate

Same option as for prove.

--rac-fail-cannot-reduce

Instruct the RAC execution to fail when an annotation cannot be checked. Normally the execution continues normally when an annotation cannot be checked.

2

RAC for function invariants aren’t supported yet.

6.9. The extract Command

The why3 extract command can extract programs written using the WhyML language (extension .mlw) to some other programming language. See also Section 10.2.

The command accepts three different targets for extraction: a WhyML file, a module, or a symbol (function, type, exception). To extract all the symbols from every module of a file named f.mlw, one should write

why3 extract -D <driver> f.mlw

To extract only the symbols from module M of file f.mlw in directory <dir>, one should write

why3 extract -D <driver> -L <dir> f.M

To extract only the symbol s (a function, a type, or an exception) from module M of file f.mlw, one should write

why3 extract -D <driver> -L <dir> f.M.s

Note the use of why3 -L, when extracting either a module or a symbol, in order to state where to look for file f.mlw.

-o <file|dir>

Output extracted code to the given file (for --flat) or directory (for --modular).

-D <driver>, --driver=<driver>

Use the given driver.

--flat

Perform a flat extraction, i.e., everything is extracted into a single file. This is the default behavior. If option -o is omitted, the result of extraction is printed to the standard output.

--modular

Extract each module in its own, separate file. Option -o is mandatory; it should be given the name of an existing directory. This directory will be populated with the resulting OCaml files.

--recursive

Recursively extract all the dependencies of the chosen entry point. This option is valid for both --modular and --flat options.

6.10. The realize Command

Why3 can produce skeleton files for proof assistants that, once filled, realize the given theories. See also Section 11.2.

6.11. The wc Command

Why3 can give some token statistics about WhyML source files.