Frama-C-discuss mailing list archives

This page gathers the archives of the old Frama-C-discuss archives, that was hosted by Inria's gforge before its demise at the end of 2020. To search for mails newer than September 2020, please visit the page of the new mailing list on Renater.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Frama-c-discuss] existential variables in ACSL spec in Frama-C/WP Sodium

  • Subject: [Frama-c-discuss] existential variables in ACSL spec in Frama-C/WP Sodium
  • From: junkil.park at (Junkil (David) Park)
  • Date: Sun, 29 Mar 2015 21:06:46 -0400


There seems to be something wrong with Frama-C/WP (Sodium) with 5 or more
existential variables in the specification.

// dummy.c
void dummy()
double d = 7;
//@ assert \exists real r1, r2, r3, r4, r5; d == r1 + r2 + r3 + r4 + r5;

> frama-c -wp dummy.c
[kernel] Parsing FRAMAC_SHARE/libc/__fc_builtin_for_normalization.i (no
[kernel] Parsing dummy.c (with preprocessing)
[wp] Running WP plugin...
[wp] Collecting axiomatic usage
[wp] warning: Missing RTE guards
[wp] 1 goal scheduled
[wp] Proved goals:    0 / 1

In the example above, Frama-C/WP doesn't try to prove it.

In addition, for the command below, it generate nothing.
> frama-c -wp -wp-prover why3 -wp-gen -wp-out dummy dummy.c

With 4 existential variables instead of 5, Frama-C/WP works fine.

Am I missing something? Or, is it an issue of the new version of Frama-C?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>