From: Christophe TROESTLER <Christophe.Troestler+ocaml@umh.ac.be>
To: rajb@rice.edu
Cc: OCaml Mailing List <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] Native code compile time question
Date: Sat, 06 Sep 2008 12:38:41 +0200 (CEST) [thread overview]
Message-ID: <20080906.123841.701792179953668400.Christophe.Troestler+ocaml@umh.ac.be> (raw)
In-Reply-To: <48C15DA2.6060800@rice.edu>
Hi,
On Fri, 05 Sep 2008 11:26:10 -0500, Raj Bandyopadhyay wrote:
>
> On using my code generator on a large program, I generate a file
> containing about 75K lines of OCaml. The native code compiler takes
> more than 30 *minutes* to compile this file! The bytecode compiler
> takes about 5 secs.
Are you speaking of ocamlopt (a bytecode program) or ocamlopt.opt (a
native code program) ?
C.
prev parent reply other threads:[~2008-09-06 10:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-05 16:26 Raj Bandyopadhyay
2008-09-05 21:32 ` [Caml-list] " Basile STARYNKEVITCH
2008-09-05 22:46 ` Jon Harrop
2008-09-05 22:44 ` Jon Harrop
2008-09-06 10:01 ` Richard Jones
2008-09-06 10:38 ` Christophe TROESTLER [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=20080906.123841.701792179953668400.Christophe.Troestler+ocaml@umh.ac.be \
--to=christophe.troestler+ocaml@umh.ac.be \
--cc=caml-list@yquem.inria.fr \
--cc=rajb@rice.edu \
/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).