From: moj@tanssi.net (Matti Jokinen)
To: Raphael Proust <raphlalou@gmail.com>
Cc: SerP <serp256@gmail.com>, caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] Very slow compilation
Date: Wed, 14 Mar 2012 00:02:02 +0200 [thread overview]
Message-ID: <20120313220202.GA29196@kiuru> (raw)
In-Reply-To: <CAAmHUA=m1Vtiksi7LTEaGHG2NiDZpwsWRb+UTdQL+Ne5-Eg98Q@mail.gmail.com>
> When working with ocamlduce (a few years ago) the same problem was
> raised. A simple thing that can greatly reduce typing time is putting
> explicit type annotations. Although the verbosity is increased it is
> not that much of a burden if the annotated parts do not evolve too
> much.
In my experience, ocamlduceopt/ocamlduceopt.opt slows down regularly when
the source file approaches 1000 lines of OCamlDuce code. The compilation
time then grows rapidly: in this machine (Thinkpad R5000) 1000 lines
took 20 seconds, 2000 lines 2 minutes, 3000 lines hanged the system.
Only OCamlDuce code causes slowdown, pure OCaml is compiled rapidly even
by OCamlDuce compilers.
However, it is not typechecking that takes time. The time-consuming
step appears to be register allocation. Try:
ocamldebug /usr/bin/ocamlduceopt -c big_ocamlduce_module.ml
run
... wait about two minutes and press control-C
You will probably find the compiler executing a function from modules
such as Interf, Coloring or Spill, or a lower level function called
from these modules.
I have never observed anything similar in OCaml, but ocamlduceopt
appears to use unmodified ocamlopt code generation modules. I wonder
what is the critical difference between OCamlDuce code and typical
OCaml code at this level.
- Matti Jokinen
next prev parent reply other threads:[~2012-03-13 22:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-11 8:11 SerP
2012-03-11 8:39 ` Gabriel Scherer
2012-03-11 9:04 ` Adrien
2012-03-11 9:21 ` Raphael Proust
2012-03-13 22:02 ` Matti Jokinen [this message]
2012-03-13 22:46 ` Gerd Stolpmann
2012-03-14 5:33 ` Gabriel Scherer
2012-03-14 8:52 ` Pierre Chambart
2012-03-13 16:58 ` Richard W.M. Jones
2012-03-14 14:45 tools
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=20120313220202.GA29196@kiuru \
--to=moj@tanssi.net \
--cc=caml-list@inria.fr \
--cc=raphlalou@gmail.com \
--cc=serp256@gmail.com \
/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