According to the C standard, section 6.5.5 §6:
"If the quotient a/b is representable, the expression (a/b)*b + a%b shall equal a;
otherwise, the behavior of both a/b and a%b is undefined."

When an invalid status is emitted for the instance of a precondition at a
callsite, registers as "high priority" the instance as well as the precondition
itself.

In offsetmaps, removes a reference to change the feedback emitted when
approximating the write of large memory locations.

Instead, the main offsetmap functor takes an additional parameter about
whether such messages should be emitted. Only the offsetmaps build by the
Eva cvalue domain emits these messages, as write approximations may have a
significant impact on the analysis precision.
Offsetmaps used to represent memory zones or dependiencies do not emit
these messages, which were most often insignificant and instable
(as many plug-ins and Eva domains use memory zones in various ways).

Andre Maroneze authored 6 months ago and David Bühler committed 6 months ago

Without escaping strings such as variable names, the produced .dot file
might print '\result' as a variable name, which results in '\r' being
stripped. Dot will then show edges such as 'esult<main>'.

The first run has no absolute valid range.
The second run only tests function copy_0 with absolute valid range.

Valentin Perrelle authored 1 year ago and David Bühler committed 9 months ago

- for imprecise.i, the equality domain does not keep an equality with
  sizeof since the sizeof is now normalized to it's constant equivalent;
  the dependency to a variable of an incomplete type disapear
- for the other tests only the order of string bases changes

David Bühler authored 11 months ago and Andre Maroneze committed 11 months ago

Thus, red statuses are only reported at the end of an analysis.

No need to reset the current location after the analysis of a function or
after calling a visitor, as the new API ensures that this is the case.

Do not add a unique id into the origin datatype, as this interacts badly with
hashconsing.
Instead, binds each origin to a unique id in the global table used to record
garbled mix history.

Prints the number of statements at which a garbled mix from a given origin
has been read and propagated, instead of the total number of times such a
garbled mix has been read/propagated.
This is more stable and depends less on states partitioning.