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] one initialisation of loop invariant is not listed in jessie GUI, this time I am sure

  • Subject: [Frama-c-discuss] one initialisation of loop invariant is not listed in jessie GUI, this time I am sure
  • From: virgile.prevosto at cea.fr (Virgile Prevosto)
  • Date: Mon, 20 Apr 2009 14:27:29 +0200
  • In-reply-to: <DB716CB96F534A778A29F870690DA9EE@AHARDPLACE>
  • References: <DB716CB96F534A778A29F870690DA9EE@AHARDPLACE>
Le lun 20 avr 2009 13:22:00 CEST,
"Christoph Weber" <Christoph.Weber at first.fraunhofer.de> a ?crit :

> 
> I would like to know, if 
> loop invariant \forall integer k;   
>    i <= k < length ==> 
>    \at(a[k], Here) == \at(a[k], Pre)&&
>    \at(b[k], Here) == \at(b[k], Pre);
> should be initialized.
> 
> If everything is fine in spite this fact, I would be very happy.

Yes, everything is fine: for the initialization, the resulting proof
obligation is more or less \at(a[k],Pre) == \at(a[k],Pre) (and the same
for b) which is trivially discharged by why itself. If you want to see
all proof obligations, you can use the option -why-opt '-all-vc', but
it is mainly intended for debugging purposes only.

Best regards,
-- 
Virgile Prevosto
Ing?nieur-Chercheur, CEA, LIST
Laboratoire de S?ret? des Logiciels
+33/0 1 69 08 71 83