caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Julia Lawall <julia.lawall@lip6.fr>
To: Xavier Rival <Xavier.Rival@ens.fr>
Cc: Gabriel Kerneis <gabriel@kerneis.info>,
	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 14:52:19 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.02.1310151450220.2254@hadrien> (raw)
In-Reply-To: <alpine.DEB.2.02.1310151442260.20768@ssh-di.ens.fr>

On Tue, 15 Oct 2013, Xavier Rival wrote:

> On Tue, 15 Oct 2013, Gabriel Kerneis wrote:
>
> > On Tue, Oct 15, 2013 at 02:31:17PM +0200, Xavier Rival wrote:
> > > The task that will be undertaken consists in developping front-end
> > > components for the MemCAD static analyzer, including a C front-end,
> > > syntax tree simplification, and possibly pre-analyses to be used in
> > > the MemCAD tool (the goal of this tool is to infer program
> > > invariants for codes manipulating complex memory data-structures).
> > > The components that shall be designed as part of this effort have
> > > the potential to be used by other research groups in the static
> > > analysis area.
> >
> > Out of curiosity, why don't CIL or Frama-C suit your needs?
>
> 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.

I would have thought that all of those would be the same things that make
it not good for program transformation.  At least not if you want to look
at the transformed code.  It could be OK for something like weaving
aspects, where you just want to execute the code, and want to advise the
parts that are not broken by the simplifications.

I have the impression that Frama-C does similar reorganizations.

julia

  reply	other threads:[~2013-10-15 12:52 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 [this message]
2013-10-15 13:02     ` David MENTRE
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=alpine.DEB.2.02.1310151450220.2254@hadrien \
    --to=julia.lawall@lip6.fr \
    --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;
as well as URLs for NNTP newsgroup(s).