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] wp loop invariant problem
- Subject: [Frama-c-discuss] wp loop invariant problem
- From: pascal.cuoq at gmail.com (Pascal Cuoq)
- Date: Wed, 29 Jun 2011 11:01:08 +0200
- In-reply-to: <BANLkTimwM8npVKAw0v11ThOOFJPVv8otpQ@mail.gmail.com>
- References: <BANLkTimwM8npVKAw0v11ThOOFJPVv8otpQ@mail.gmail.com>
> But in the file "max_element2.c", in Line 47, > I replace "loop invariant !(\exists integer k; 0 <= k < i && (a[max] < > a[k]));" > with "loop invariant IsMaximum(a, i, max);" which are the same. > But in this case, Frama-C can not prove. It's only a bug in Frama-C if Frama-C generates an obligation that is not provable. Did you look at the generated obligation? It often happens that adding a layer of definition prevents automatic provers to conclude on a property that was provable when it was simple. Which automatic prover(s) did you use? Pascal
- References:
- [Frama-c-discuss] wp loop invariant problem
- From: marsishandsome at gmail.com (mars Gu)
- [Frama-c-discuss] wp loop invariant problem
- Prev by Date: [Frama-c-discuss] wp loop invariant problem
- Next by Date: [Frama-c-discuss] wp loop invariant problem
- Previous by thread: [Frama-c-discuss] wp loop invariant problem
- Next by thread: [Frama-c-discuss] wp loop invariant problem
- Index(es):