From: David MENTRE <dmentre@linux-france.org>
To: Xavier Rival <Xavier.Rival@ens.fr>
Cc: Gabriel Kerneis <gabriel@kerneis.info>,
caml users <caml-list@inria.fr>,
ocaml-jobs@inria.fr
Subject: Re: [Caml-list] [ocaml-jobs] Developper position: designing a C front-end in OCaml
Date: Tue, 15 Oct 2013 15:02:23 +0200 [thread overview]
Message-ID: <CAC3Lx=abf-PJWAPM=KS57bhsFZj==Hi5Uia7xZH4NTjFt6Oyxw@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1310151442260.20768@ssh-di.ens.fr>
Hello,
2013/10/15 Xavier Rival <Xavier.Rival@ens.fr>:
> I have used CIL in another project in the past. My experience is that it is
> a great front-end for program transformation. It is less adapted to static
> analysis though, as it does a lot of syntactic transformations, causing part
> of the structure of the code to be lost. For instance, it transforms loops
> into a while(1) form, with break statements. This design choice does not
> help static analyzers, and may require recalculating information that was
> lost in the early phases.
In that case, why don't you extend CIL to fix its deficiencies? It
would help other projects using CIL like Frama-C.
In the same way, why do you implement your own C parsing
infrastructure and do not build a Frama-C plug-in for your analysis?
Frama-C has already a user base (industrial and academic), if you can
improve it it would help a lot. And it would allow to combine your
analysis with other Frama-C plug-ins.
Last but not least, you say "We plan to release source code of the
analyzer along the course of the project." Which kind of licence do
you plan to use?[1]
Sincerely yours,
david
[1] I am maintaining this directory:
http://gulliver.eu.org/free_software_for_formal_verification
next prev parent reply other threads:[~2013-10-15 13:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-15 12:31 [Caml-list] " Xavier Rival
2013-10-15 12:41 ` Gabriel Kerneis
2013-10-15 12:48 ` [Caml-list] [ocaml-jobs] " Xavier Rival
2013-10-15 12:52 ` Julia Lawall
2013-10-15 13:02 ` David MENTRE [this message]
2013-10-15 13:22 ` Gabriel Kerneis
2013-10-15 18:29 ` Dmitry Grebeniuk
2013-10-15 21:36 ` Gabriel Kerneis
2013-10-16 0:12 ` Wojciech Meyer
2013-10-16 6:12 ` David MENTRE
2013-10-15 18:13 ` Florian Weimer
2013-10-15 14:06 ` [Caml-list] " Basile Starynkevitch
2013-10-15 15:36 ` Wojciech Meyer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAC3Lx=abf-PJWAPM=KS57bhsFZj==Hi5Uia7xZH4NTjFt6Oyxw@mail.gmail.com' \
--to=dmentre@linux-france.org \
--cc=Xavier.Rival@ens.fr \
--cc=caml-list@inria.fr \
--cc=gabriel@kerneis.info \
--cc=ocaml-jobs@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox