From: Wojciech Meyer <wojciech.meyer@gmail.com>
To: Basile Starynkevitch <basile@starynkevitch.net>
Cc: Xavier Rival <Xavier.Rival@ens.fr>, Caml List <caml-list@inria.fr>
Subject: Re: [Caml-list] Developper position: designing a C front-end in OCaml
Date: Tue, 15 Oct 2013 16:36:49 +0100 [thread overview]
Message-ID: <CAOg1smCCaSoiifuGMRqAVo4MTRN5oQKEmOMnHFnfw3OXkAdu5Q@mail.gmail.com> (raw)
In-Reply-To: <20131015140624.GA24254@ours.starynkevitch.net>
[-- Attachment #1: Type: text/plain, Size: 2099 bytes --]
Hello,
So there are at least:
- cfront [1]
- yacfe [2]
- CIL
do we need yet another frontend in the compiler community? Just a
digression.
Wojciech
[1] http://www.irit.fr/recherches/ARCHI/MARCH/rubrique.php3?id_rubrique=61
[2] http://padator.org/software-yacfe.php
On Tue, Oct 15, 2013 at 3:06 PM, Basile Starynkevitch <
basile@starynkevitch.net> wrote:
> On Tue, Oct 15, 2013 at 02:31:17PM +0200, Xavier Rival wrote:
> >
> > We are looking for an experienced OCaml developper in order to
> > design front-end components for a static analyzer developped as part
> > of the MemCAD ERC project (http://www.di.ens.fr/~rival/memcad.html).
>
>
> If you want to develop in Ocaml CIL is definitely a possible way to go
> (and you could also code a Frama-C plugin, hence taking advantage of
> existing Frama-C infrastructure). If it does not fit all of
> your needs, please contribute your enhancements to it.
>
> Alternatively, Did you consider working inside GCC, perhaps thru a plugin,
> perhaps using MELT, a domain specific language to extend GCC, see
> http://gcc-melt.org/ ?
> you could take advantage of existing GCC infrastructure, in particular
> add some analysis pass after some existing GCC optimizing passes which
> would have already done some transformations (And MELT is not Ocaml,
> but a Lisp-like language, notably enabling you to code in a
> functional style - more than if you did your GCC extension in C++03).
>
> At last you could work with CompCert http://compcert.inria.fr/
> which can be viewed as a C compiler coded in Ocaml (although it is much
> more
> than that).
>
> Regards.
> --
> Basile STARYNKEVITCH http://starynkevitch.net/Basile/
> email: basile<at>starynkevitch<dot>net mobile: +33 6 8501 2359
> 8, rue de la Faiencerie, 92340 Bourg La Reine, France
> *** opinions {are only mines, sont seulement les miennes} ***
>
> --
> Caml-list mailing list. Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
[-- Attachment #2: Type: text/html, Size: 3457 bytes --]
prev parent reply other threads:[~2013-10-15 15:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-15 12:31 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
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 [this message]
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=CAOg1smCCaSoiifuGMRqAVo4MTRN5oQKEmOMnHFnfw3OXkAdu5Q@mail.gmail.com \
--to=wojciech.meyer@gmail.com \
--cc=Xavier.Rival@ens.fr \
--cc=basile@starynkevitch.net \
--cc=caml-list@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