In domains, changes [Store.register_global_state] that now takes a boolean
argument indicating whether the domain states must be saved during the
analysis.

The function given to [dynamic_register] builds directly the flag instead of
only the abstraction.

The name, description, priority and the experimental boolean are now arguments
of the register function. The priority and the experimental boolean are optional.
The function returns the flag that allows enabling programmatically the domain.

New field [experimental] to register a domain in abstractions.ml.
New warning key experimental, that replaces the debug key experimental-ok.

For the time being, these options are kept to maintain backward compatibility.
They are now invisible and produce a warning if used.
They are automatically generated when a domain is registered, and they simply
set up the -eva-domains option.

In the engine, registered domains must provide a description.
The domains description is printed on -eva-domains help or -eva-domains list.

Starting with the most useful domains.
The order of registration is also the order in which domains are listed in the
help message of the -eva-domains option.

Exports 4 new functions in ival:
- is_int and is_float
- is_small_set and project_small_set

Domains are built by increasing order of priority, so domains with higher
priority are added at the top of the domains tree, and thus are processed
first during the analysis.

This ensures that the cvalue domain (and other optimized domains) are always
called first in the engine.

Do not lift the abstract locations if it is not needed.

Domain_product works on Internal modules.
Location_lift and Domain_lift promote leaf modules into internal modules,
by creating the suitable structure.

Complete rewrite of abstraction.ml, with even more first class modules and GADT.
All current abstract values and domains are registered with this generic
mecanism in abstractions.ml, except the Apron binding and the Numerors domain.

The configuration is now the set of abstractions that should be instantiated.

Keys for abstract values, locations and states are created in structure.ml.
Shapes are created in the respective modules Value, Location and Domain
in abstract.ml.

These module definitions were previously in abstract_value, abstract_location
and abstract_domain. They are now grouped in this new file for the three
abstractions.
These module types should only be useful for the engine, and need not to be
visible in the implementation of the various abstractions.

New module type Leaf in abstract_value, abstract_location and abstract_domain
with the key identifying the module. The internal structure is no longer needed
in these abstractions, and is instead built by the engine from this key.

Keys are no longer exported outside the modules.
For abstract domains, the key is automatically created by the functor
Domain_builder.Complete from the domain name.

Many changes throughout the analyzer:
- in the engine, Abstract_value.{Internal|External} becomes
  Abstract.Value.{Internal|External}.
- in the abstractions, Abstract_value.Internal becomes Abstract_value.Leaf.

François Bobot authored 7 years ago and David Bühler committed 5 years ago

   - Top for loops

This module type simplifies the signature of functors using evaluation
functions.