Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Christophe Raffalli <christophe.raffalli@univ-savoie.fr>
To: caml-list@inria.fr
Subject: Stack overflow with native code
Date: Sun, 23 Dec 2007 16:04:50 +0100	[thread overview]
Message-ID: <476E7912.10005@univ-savoie.fr> (raw)


Dear list members,

I have a program that runs well and quick (0.6s) in bytecode but 
produces a stackoverflow on native code (in 0.2s).
This behavior is observed on linux intel with unlimited stack size and 
OS X with 64Mb stacks (which is the maximum).
The only unsafe feature are one or two magic in bindlib to manage a 
dependtly type environment. There is no C interface
and no use of any C library, and no -unsafe. So I do not really see how 
to explain the difference of behavior.

I tested with ocaml 3.10 and 3.10.1-rc1

Any hints ? (if not, I will fill a bug report, but the piece of code to 
compile to reproduce the problem is large (~10000 loc)).

Cheers,
Christophe


                 reply	other threads:[~2007-12-23 15:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=476E7912.10005@univ-savoie.fr \
    --to=christophe.raffalli@univ-savoie.fr \
    --cc=caml-list@inria.fr \
    /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