From: Richard Jones <rich@annexia.org>
To: Jon Harrop <jon@ffconsultancy.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] ocamlopt stack overflowing
Date: Mon, 23 May 2005 23:45:07 +0100 [thread overview]
Message-ID: <20050523224507.GA25635@furbychan.cocan.org> (raw)
In-Reply-To: <200505232207.00090.jon@ffconsultancy.com>
On Mon, May 23, 2005 at 10:06:59PM +0100, Jon Harrop wrote:
>
> I've got a problem with ocamlopt stack overflowing on some generated OCaml
> source (one 1,227-line function, 288kB of source). Any ideas what the cause
> is?
>
> I suspect that compiling the OCaml distribution from source and using
> ocamlopt.opt will do the trick otherwise.
We've seen this before (on Windows) and the solution was
export OCAMLRUNPARAM=l=16M
(for reasons which I forget now, we were using the bytecode ocamlopt,
not ocamlopt.opt).
Rich.
--
Richard Jones, CTO Merjis Ltd.
Merjis - web marketing and technology - http://merjis.com
Team Notepad - intranets and extranets for business - http://team-notepad.com
next prev parent reply other threads:[~2005-05-23 22:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-23 21:06 Jon Harrop
2005-05-23 22:45 ` Richard Jones [this message]
2005-05-24 1:10 ` [Caml-list] " Jon Harrop
2005-05-24 9:58 ` Damien Doligez
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=20050523224507.GA25635@furbychan.cocan.org \
--to=rich@annexia.org \
--cc=caml-list@inria.fr \
--cc=jon@ffconsultancy.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;
as well as URLs for NNTP newsgroup(s).