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
b8558b55
Commit
b8558b55
authored
9 months ago
by
Loïc Correnson
Browse files
Options
Downloads
Patches
Plain Diff
[region] README
parent
82520f64
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
src/plugins/region/README.md
+56
-1
56 additions, 1 deletion
src/plugins/region/README.md
with
56 additions
and
1 deletion
src/plugins/region/README.md
+
56
−
1
View file @
b8558b55
# Region Analysis plugin
# Region Analysis plugin
(experimental)
Region is a plugin for Frama-C that implements a new memory and alias analysis.
This is a work in progress in early design stage.
## Usage
Regions are computed on demand from the registered Server requests.
Command line option
`-region`
can be used to compute regions for all functions
and dump on output the result analysis. With
`-region-debug 1+`
typed accesses
are also reported.
An API will be provided soon.
## Annotations
Behavior annotation
`\region::region`
and code annotation
`\region::alias`
can be used to specify supplementary aliases and to name regions.
The syntax is the same:
```
//@ region [A:] lv, … , lv ;
```
Such a specification put all the l-values in the same region. A name can be
given to the region, and reused later to put other l-values on the same region.
Several regions can be specified in a single annotation.
Unnamed regions from different annotations refer to _different_ regions unless
they are aliased by sharing common l-values.
L-values in region annotations use a similar syntax to ACSL terms.
However, array access and pointer arithmetics must be specified with unlimited range, eg.
`a[..]`
or
`*(p+(..))`
.
A syntax for specifying field aliasing and input/output array shapes will be provided soon.
## Current Limitations
Currently, ACSL contracts are not taken into account except for region
annotations. Function calls are totally incomplete, and aliases that would be
produces by function calls are not _yet_ taken into account. Use
`//@alias`
code-annotations as a temporary work around.
## Ivette Support
The Region Analysis component can be used to compute and visualize regions.
Tooltips print access types to each regions.
Colored regions means the following:
-
_Red_ regions are those accessed with incompatible types
-
_Yellow_ regions are constant pointers
-
_Orange_ regions are written pointers
-
_Green_ regions are RW regions
-
_Pink_ regions are written-only regions (might be drop)
-
_Grey_ regions are read-only regions (constant, no memory)
Regions access and localization of currently selected marker will be
provided soon.
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