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.

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

- Fix Value/Value#5
- Fix Value/Value#14

Some case studies (e.g. dyad) use some ugly casts from fd_set_t which lead
to the analysis stopping too early.
Changing the representation of fd_set_t should also help it better conform to
the standard (since a fd_set_t should be able to hold FD_SETSIZE elements).

[Ptests] preserve LOG after STDOPT directive

See merge request frama-c/frama-c!2073

This is absolutely not a sneaky attempt to relaunch a build (now that OCI seems
in better shape) pushing a nearly empty commit.