Maxime Jacquemin authored 5 months ago and David Bühler committed 1 month ago

The parser used to always assign the [lower], [nearest] and [upper]
to the same constant for any hexadecimal float. Which is obviously
wrong.

It is fixed by using [float_of_string] and rounding modes to compute
upper and lower bounds.

In all files, all occurrences of "[eva] done for function" have been replaced
by "[eva] Done for function".

- always remove FC's internal attribute everywhere before deciding whether
  a cast is needed.
- ACSL and C decisions to cast are similar
- only unroll type for checking equality. If a cast is needed, keep
  typedef (if any) as target

original definitions took advantage of the non-compliant behavior
wrt decimal integer litteral

- warns only on fundamental types reads

- RTE is stricter than C for unsigned chars
- RTE does not warn on initialization for structs/union

presence of an offset does not mean that we could write a spurious value through
a union.

Only modifications introduced by non necessary casts elimination

Only differences comes from using float builtins in expr-to-term