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] Debugging huge theories
- Subject: [Frama-c-discuss] Debugging huge theories
- From: yegor.derevenets at gmail.com (Yegor Derevenets)
- Date: Mon, 28 Dec 2009 03:02:19 +0300
- In-reply-to: <699ab5ba0912220218u731e45cem8a3d0e0918e84177@mail.gmail.com>
- References: <699ab5ba0912211750v66d27a0fh6d259e7c1e85b307@mail.gmail.com> <9AB2B446-D6EF-4E9D-BA6F-CA54D9796FC3@first.fraunhofer.de> <699ab5ba0912220218u731e45cem8a3d0e0918e84177@mail.gmail.com>
Hello, All! 2009/12/22 Yegor Derevenets <yegor.derevenets at gmail.com>: > Obviously, some annotation are wrong (the function is not trivial, > and I'm a human). The quesiton is how to detect which and why, > and fix them in a reasonable amount of time. Maybe some ideas > about what to begin with? Option -jessie-why-opt=-fast-wp helps much to decrease size of theory (thanks twitter.com/frama_c for this hint). Now after careful rewriting of annotations I have only 213 lemmas against >2000 in the past and 34 to prove, which seems more manageable. I think, question is closed. -- Yegor Derevenets
- References:
- [Frama-c-discuss] Debugging huge theories
- From: yegor.derevenets at gmail.com (Yegor Derevenets)
- [Frama-c-discuss] Debugging huge theories
- From: jens.gerlach at first.fraunhofer.de (Jens Gerlach)
- [Frama-c-discuss] Debugging huge theories
- From: yegor.derevenets at gmail.com (Yegor Derevenets)
- [Frama-c-discuss] Debugging huge theories
- Prev by Date: [Frama-c-discuss] Loop Termination Challenge
- Previous by thread: [Frama-c-discuss] Debugging huge theories
- Next by thread: [Frama-c-discuss] Loop Termination Challenge
- Index(es):