On Mon, 3 May 2004, Jacques Carette wrote:

> > Do you have an explanation for this fact ?  Given that ocamlopt can inline
> > function and propagate constants across compilation unit boundaries, what
> > kind of extra optimizations do you get with a single compilation unit ?
>
> It appears to be inlining of functions across compilation unit boundaries
> that makes the difference.

Well, precisely, ocamlopt can inline accross compilation unit boundaries,
so what's the benefit of having a single compilation unit ?

> Note that this is second-hand, if people really want to know details, it
> would take me a couple of days to get them from the right people.

FWIW, I just tried to put all the .ml/.mli of a medium-sized project (18
kloc) into a single file. Observations:

- ocamlopt crashes because of a stack overflow; ocamlopt.opt works fine.
- compilation is about 3 times slower.
- there is no noticeable difference on the runtime performance.


-- Alain

-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners