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-discuss Digest, Vol 63, Issue 2
- Subject: [Frama-c-discuss] Frama-c-discuss Digest, Vol 63, Issue 2
- From: Pierre-Loic.Garoche at onera.fr (Pierre-Loïc Garoche)
- Date: Fri, 9 Aug 2013 14:00:45 +0200
- In-reply-to: <D63ADA18-CFF2-439D-B6A9-5C763228E98E@fokus.fraunhofer.de>
- References: <mailman.27.1376042548.3402.frama-c-discuss@lists.gforge.inria.fr> <D63ADA18-CFF2-439D-B6A9-5C763228E98E@fokus.fraunhofer.de>
Hi Jens, > > int x = 0; > > > > /*@ requires y >= 0; > > @ ensures \result > x; > > @*/ > > int f(int y) { return y +1; } > > > in my opinion the function cannot be verified because the operation y+1 might overflow > in which case the result can become negative. Yes, you are right. But my main issue was that - if you use Coq for example - execpt the type of x, nothing is known about its value. I was looking for a minimal example. You have the same issue with an additional requires y < 10: -- Pierre-Lo?c Garoche Research Scientist @ ONERA pierre-loic.garoche at onera.fr - pierre-loic-garoche at uiowa.edu http://www.onera.fr/staff/pierre-loic-garoche/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: <http://lists.gforge.inria.fr/pipermail/frama-c-discuss/attachments/20130809/2010d432/attachment.pgp>
- References:
- [Frama-c-discuss] Frama-c-discuss Digest, Vol 63, Issue 2
- From: jens.gerlach at fokus.fraunhofer.de (Gerlach, Jens)
- [Frama-c-discuss] Frama-c-discuss Digest, Vol 63, Issue 2
- Prev by Date: [Frama-c-discuss] ACSL, globals and ghosts
- Next by Date: [Frama-c-discuss] ACSL, globals and ghosts
- Previous by thread: [Frama-c-discuss] Frama-c-discuss Digest, Vol 63, Issue 2
- Next by thread: [Frama-c-discuss] Runtime problem on ARM
- Index(es):