Commit 4c29c7bb authored by Virgile Prevosto's avatar Virgile Prevosto
Browse files

shorter option name for separating annotations + update README

parent 1815c5ce
......@@ -31,6 +31,11 @@ generated from a given meta-property. This name is of the form `_nnn`, where `nn
is unique within each annotated function. Hence, with this option, each generated `meta` assertion
is identified uniquely by the `property_name`, the function to which it belongs, and this id.
Finally, generated annotations are normally tied to the statement upon which
they apply. Option `-meta-separate-annots` will generate no-op instructions and
tie each annotation to a separate instruction, forcing the order in which they
ought to be considered.
Several other options are available: use `frama-c -meta-h` for more information.
## Basic meta-property
......
......@@ -89,7 +89,7 @@ module Static_bindings = Self.Int (struct
end)
module Separate_annots = Self.False (struct
let option_name = "-meta-separate-annot-instruction"
let option_name = "-meta-separate-annots"
let help =
"When set, each generated statement annotation will be tied to its own \
(nop) instruction. Otherwise (default), all annotations generated for \
......
/* run.config
OPT: @META@ -meta-number-assertions @PRINT@
OPT: @META@ -kernel-verbose 0 -meta-separate-annot-instruction @PRINT@
OPT: @META@ -kernel-verbose 0 -meta-separate-annots @PRINT@
*/
int *p1;
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment