Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
F
frama-c
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Container Registry
Model registry
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
pub
frama-c
Commits
a52e5e61
Commit
a52e5e61
authored
1 year ago
by
Allan Blanchard
Browse files
Options
Downloads
Patches
Plain Diff
[doc] Minor corrections in user manual and fix typos
parent
4f16554b
No related branches found
No related tags found
No related merge requests found
Changes
3
Hide whitespace changes
Inline
Side-by-side
Showing
3 changed files
doc/userman/user-acsl.tex
+5
-4
5 additions, 4 deletions
doc/userman/user-acsl.tex
tests/libc/stdlib_c.c
+1
-1
1 addition, 1 deletion
tests/libc/stdlib_c.c
tests/libc/string_c.c
+1
-1
1 addition, 1 deletion
tests/libc/string_c.c
with
7 additions
and
6 deletions
doc/userman/user-acsl.tex
+
5
−
4
View file @
a52e5e61
...
...
@@ -6,14 +6,15 @@
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|
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 useful
l
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
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
ignored with a warning, unlike
\lstinline
|unroll
_
| which by default will be
treated as a user error.
ignored with a warning, whereas
\lstinline
|unroll
_
| cannot be identified as
being supported by Eva, which means that it can only be treated as a user
error.
\section
{
Handling indirect calls with
\texttt
{
calls
}}
\label
{
acsl:calls
}
...
...
This diff is collapsed.
Click to expand it.
tests/libc/stdlib_c.c
+
1
−
1
View file @
a52e5e61
...
...
@@ -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-no-alloc-returns-null -eva-msg-key malloc"
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)
#include
"stdlib.c"
...
...
This diff is collapsed.
Click to expand it.
tests/libc/string_c.c
+
1
−
1
View file @
a52e5e61
/* run.config
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"
volatile
int
v
;
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment