On 09-12-2008, Gilles Pirio <
gilles.pirio@gmail.com> wrote:
>> 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?
>
>