caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Gilles Pirio" <gilles.pirio@gmail.com>
To: "Sylvain Le Gall" <sylvain@le-gall.net>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Re: Ocaml back-end
Date: Tue, 9 Dec 2008 15:51:34 +0000	[thread overview]
Message-ID: <b3515bd20812090751l58f1c5b8n7d8b6e889c793e66@mail.gmail.com> (raw)
In-Reply-To: <slrngjohnq.r7s.sylvain@gallu.homelinux.org>

[-- Attachment #1: Type: text/plain, Size: 2284 bytes --]

Hello
Ok, thanks for the feedback.

> To my mind, the best way is to provide a patch through the bug tracking
> system of INRIA. This is highly probable that INRIA team doesn't accept
> it directly but ask you to justify/modify it in order to fit the whole
> compiler -- which could be quiet a long process in fact.

It would greatly help to know what the INRIA team would consider as
acceptable ahead of doing the work. What kind of guidlines would you
advise me to follow? I guess I can add new passes but can I modify
existing ones?

The ideal solution would be to open the back-end using the dynlink
library. I've done it with 3.11 to speed up development. The back-end is now
a cmo file. I separately compile copt0.cmo, copt1.cmo... with different
back-ends. Then I can use command like: ocamlopt -copt copt0.cmo myfile.ml
to compile with my back-end.
But even though that's a small change I'm not sure the INRIA guys would
like it, right?


> Well, I can give you access to an unofficial public git mirror of
> INRIA's cvs.  I use it to build my compiler, but I dunno if anyone else
> uses it.  If it had optimizations like this, they might very well.

That sounds great, thanks. I'll follow up when I have the need to do that
(e.g. when
I get the above info and actually start the work).

Cheers
G<>



On Sun, Dec 7, 2008 at 9:58 PM, Sylvain Le Gall <sylvain@le-gall.net> wrote:

> Hello,
>
> On 06-12-2008, Gilles Pirio <gilles.ocaml@googlemail.com> wrote:
> > (2) Any way to contribute this work back to Ocaml community (on a
> > separate cvs branch?) or is this kind of work planned by the core
> > Ocaml team?
> >
>
> To my mind, the best way is to provide a patch through the bug tracking
> system of INRIA. This is highly probable that INRIA team doesn't accept
> it directly but ask you to justify/modify it in order to fit the whole
> compiler -- which could be quiet a long process in fact.
>
> http://caml.inria.fr/mantis/
>
> Regards,
> Sylvain Le Gall
>
> _______________________________________________
> Caml-list mailing list. Subscription management:
> http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
> Archives: http://caml.inria.fr
> 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: 3231 bytes --]

  reply	other threads:[~2008-12-09 15:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-06 12:48 Gilles Pirio
2008-12-06 20:02 ` [Caml-list] " Edgar Friendly
2008-12-07 21:58 ` Sylvain Le Gall
2008-12-09 15:51   ` Gilles Pirio [this message]
2008-12-09 19:31     ` Sylvain Le Gall
2009-01-13 19:09       ` [Caml-list] " Gilles Pirio
2009-01-13 20:44         ` Sylvain Le Gall

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=b3515bd20812090751l58f1c5b8n7d8b6e889c793e66@mail.gmail.com \
    --to=gilles.pirio@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=sylvain@le-gall.net \
    /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).