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] Frama-C/WP and CVC4 (version 1.5)
- Subject: [Frama-c-discuss] Frama-C/WP and CVC4 (version 1.5)
- From: jens.gerlach at fokus.fraunhofer.de (Gerlach, Jens)
- Date: Sat, 5 Aug 2017 14:09:39 +0000
Hello, in âACSL by Exampleâ (https://fraunhoferfokus.github.io/acsl-by-example/), we have been using the prover CVC4 (http://cvc4.cs.stanford.edu/web/) for quite some time. Recently, a new version (1.5) was released. Unfortunately, it appears that this new version can discharge considerably fewer of our proof obligations than the previous release 1.4. Here is a short list that highlights the issue. Example 1.4 1.5 accumulate 8 1 adjacent_difference 23 0 adjacent_difference_inv 20 3 adjacent_find 9 1 binary_search 2 0 binary_search2 3 0 copy 12 1 copy_backward 12 1 count 10 3 equal 1 1 equal_range 3 0 equal_range2 36 4 I wonder, whether other WP users also observe this problem. Maybe there is fancy option that one should supply to CVC4-1.5 (through why3)? If you know of one, then please let me know! Regards Jens
- Follow-Ups:
- [Frama-c-discuss] Frama-C/WP and CVC4 (version 1.5)
- From: moy at adacore.com (Yannick Moy)
- [Frama-c-discuss] Frama-C/WP and CVC4 (version 1.5)
- Prev by Date: [Frama-c-discuss] Proper usage of -wp-unalias-vars?
- Next by Date: [Frama-c-discuss] Frama-C/WP and CVC4 (version 1.5)
- Previous by thread: [Frama-c-discuss] Frama-Clang 0.0.3 - Phosphorus compatibility
- Next by thread: [Frama-c-discuss] Frama-C/WP and CVC4 (version 1.5)
- Index(es):