Skip to content
Snippets Groups Projects
Commit a52e5e61 authored by Allan Blanchard's avatar Allan Blanchard
Browse files

[doc] Minor corrections in user manual and fix typos

parent 4f16554b
No related branches found
No related tags found
No related merge requests found
...@@ -6,14 +6,15 @@ ...@@ -6,14 +6,15 @@
When a plug-in registers an extension, it can be used in \acsl annotations When a plug-in registers an extension, it can be used in \acsl annotations
with 2 different syntaxes. As an example, with an extension \lstinline|bar| with 2 different syntaxes. As an example, with an extension \lstinline|bar|
registered by the plug-in \lstinline|foo|, we can use the short syntax registered by the plug-in \lstinline|foo|, we can use the short syntax
\lstinline|bar _| and the complete syntax \lstinline|\foo::bar _|. \lstinline|bar _| or the complete syntax \lstinline|\foo::bar _|.
The complete syntax is usefull to print better warning/error messages, and to The complete syntax is useful to print better warning/error messages, and to
better understand which plug-in introduced the extension. Additionnaly, all better understand which plug-in introduced the extension. Additionnaly, all
extensions coming from an unloaded plug-in can be ignored this way. For extensions coming from an unloaded plug-in can be ignored this way. For
example, if \Eva is not loaded, \lstinline|\eva::unroll _| annotations will be example, if \Eva is not loaded, \lstinline|\eva::unroll _| annotations will be
ignored with a warning, unlike \lstinline|unroll _| which by default will be ignored with a warning, whereas \lstinline|unroll _| cannot be identified as
treated as a user error. being supported by Eva, which means that it can only be treated as a user
error.
\section{Handling indirect calls with \texttt{calls}} \section{Handling indirect calls with \texttt{calls}}
\label{acsl:calls} \label{acsl:calls}
......
...@@ -2,7 +2,7 @@ ...@@ -2,7 +2,7 @@
STDOPT: #"-eva-no-builtins-auto -eva-slevel 10 -eva-builtin calloc:Frama_C_calloc -eva-alloc-builtin by_stack -eva-msg-key malloc" STDOPT: #"-eva-no-builtins-auto -eva-slevel 10 -eva-builtin calloc:Frama_C_calloc -eva-alloc-builtin by_stack -eva-msg-key malloc"
STDOPT: #"-eva-no-builtins-auto -eva-slevel 10 -eva-builtin calloc:Frama_C_calloc -eva-alloc-builtin by_stack -eva-no-alloc-returns-null -eva-msg-key malloc" STDOPT: #"-eva-no-builtins-auto -eva-slevel 10 -eva-builtin calloc:Frama_C_calloc -eva-alloc-builtin by_stack -eva-no-alloc-returns-null -eva-msg-key malloc"
STDOPT: #"-eva-no-builtins-auto" STDOPT: #"-eva-no-builtins-auto"
*/ // \eva::slevel is used to \eva::unroll loops */ // \eva::slevel is used to unroll loops
#define malloc(n) Frama_C_malloc(n) #define malloc(n) Frama_C_malloc(n)
#include "stdlib.c" #include "stdlib.c"
......
/* run.config /* run.config
STDOPT: #"-eva-no-builtins-auto -eva-slevel 1000 -eva-no-skip-stdlib-specs" STDOPT: #"-eva-no-builtins-auto -eva-slevel 1000 -eva-no-skip-stdlib-specs"
*/ // \eva::slevel is used to \eva::unroll loops */ // \eva::slevel is used to unroll loops
#include "string.c" #include "string.c"
volatile int v; volatile int v;
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment