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] Unable to prove the example code in ACSL documentation

  • Subject: [Frama-c-discuss] Unable to prove the example code in ACSL documentation
  • From: Claude.Marche at inria.fr (Claude Marche)
  • Date: Thu, 23 Oct 2014 16:03:58 +0200
  • In-reply-to: <CA+yPOVic8ttY9=xY0gPMLfLi-T7RDsGpC5dxuQf3RO8_Z-sMag@mail.gmail.com>
  • References: <CAFMfd-wCu7sXQxDHsSWhxMUMW3uO_BhDFCirOPTdge8vv6+nbg@mail.gmail.com> <CA+yPOVic8ttY9=xY0gPMLfLi-T7RDsGpC5dxuQf3RO8_Z-sMag@mail.gmail.com>

On 10/23/2014 10:59 AM, Virgile Prevosto wrote:
> However, if we go back to your concrete example, my guess is
> that you're just missing the -wp-init-const option on the command
> line, that tells WP to assume that global const variables always have
> their initial values (const specifier is so easily abused that this
> option is not on by default).

Just a thought, not tested, why not using a logic constant instead of a 
ghost, e.g

//@ logic int *addr_x = &x;

Then it would be taken for sure that the value of addr_c is &x in

//@ assigns *addr_x;
int f(int x) {
     // ...
     return g();
}

- Claude