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: virgile.prevosto at m4x.org (Virgile Prevosto)
- Date: Thu, 23 Oct 2014 16:57:47 +0200
- In-reply-to: <54490ACE.4000901@inria.fr>
- References: <CAFMfd-wCu7sXQxDHsSWhxMUMW3uO_BhDFCirOPTdge8vv6+nbg@mail.gmail.com> <CA+yPOVic8ttY9=xY0gPMLfLi-T7RDsGpC5dxuQf3RO8_Z-sMag@mail.gmail.com> <54490ACE.4000901@inria.fr>
2014-10-23 16:03 GMT+02:00 Claude Marche <Claude.Marche at inria.fr>: > > > 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; > Indeed, this works perfectly well, I'm not sure why I didn't think about it [?] Best regards, -- E tutto per oggi, a la prossima volta Virgile -------------- section suivante -------------- Une pi?ce jointe HTML a ?t? nettoy?e... URL: <http://lists.gforge.inria.fr/pipermail/frama-c-discuss/attachments/20141023/2b1ef96d/attachment-0001.html> -------------- section suivante -------------- Une pi?ce jointe autre que texte a ?t? nettoy?e... Nom: 35F.gif Type: image/gif Taille: 540 octets Desc: non disponible URL: <http://lists.gforge.inria.fr/pipermail/frama-c-discuss/attachments/20141023/2b1ef96d/attachment-0001.gif>
- Follow-Ups:
- [Frama-c-discuss] Unable to prove the example code in ACSL documentation
- From: georgeleeliangwei at gmail.com (George Lee)
- [Frama-c-discuss] Unable to prove the example code in ACSL documentation
- References:
- [Frama-c-discuss] Unable to prove the example code in ACSL documentation
- From: georgeleeliangwei at gmail.com (gg lee)
- [Frama-c-discuss] Unable to prove the example code in ACSL documentation
- From: virgile.prevosto at m4x.org (Virgile Prevosto)
- [Frama-c-discuss] Unable to prove the example code in ACSL documentation
- From: Claude.Marche at inria.fr (Claude Marche)
- [Frama-c-discuss] Unable to prove the example code in ACSL documentation
- Prev by Date: [Frama-c-discuss] Unable to prove the example code in ACSL documentation
- Next by Date: [Frama-c-discuss] Unable to prove the example code in ACSL documentation
- Previous by thread: [Frama-c-discuss] Unable to prove the example code in ACSL documentation
- Next by thread: [Frama-c-discuss] Unable to prove the example code in ACSL documentation
- Index(es):