From: Franck Delaplace <delapla@lami.univ-evry.fr>
To: "M E Leypold @ labnet" <leypold@informatik.uni-tuebingen.de>
Cc: OCAML <caml-list@inria.fr>
Subject: Re: [Caml-list] Problem with ocamlopt
Date: Tue, 12 Mar 2002 08:30:33 +0100 [thread overview]
Message-ID: <3C8DAE99.9040309@lami.univ-evry.fr> (raw)
In-Reply-To: <15500.42189.563370.819377@hod.void.org>
[-- Attachment #1: Type: text/plain, Size: 1995 bytes --]
>
>
> > PS: You will find attached the source code
>
>When trying to read it, one of my brain modules threw an exception:
>Stack overflow. [:-)]
>
>
Thank you to attempt to read it. You're a pioneer . What does it talk
about ? :-)
>Hi Franck,
>
>Actually I only wrote to make that joke, but to be a bit more useful:
>It might be that the constructs used by the code generator you used to
>translate the FA definitions into ocaml nest somewhat too deeply, and
>since the ocamlcompiler parses recursive descendend (i think) its
>stack overflows at some point or other.
>
>
>
>Suggestions:
>
> * Try cutting down your FA, let's say to half as a test case and
> compile it then. Does it overflow still?
>
Yes it does if the code it still in a single file.
If it is splitted in more than one file it is ok
>If things are like I suggest,
> that is should be called a tagcc bug, since there is IMHO no
> reason for FA execution to use nested constructs this way
> (nesting too deeply).
>
>Regards -- Markus
>
>
>
here another Stack overflow for a simpler program
let t = [|
[|
(1,[|1 ;1;1|],1.0);
(1,[|1 ;1;1|],1.0);
(1,[|1 ;1;1|],1.0);
(1,[|1 ;1;1|],1.0)
|];
repeat the previous array more than 390 times ....
[|
(1,[|1 ;1;1|],1.0);
(1,[|1 ;1;1|],1.0);
(1,[|1 ;1;1|],1.0);
(1,[|1 ;1;1|],1.0)
|]
|] ;;
Now, if I split it into several different arrays but in the same file,
There is also the same error.
If each line is replaced by (ugly code)
let t = Array.make 400 [||] ;;
let i = ref 0 ;;
(incr i ; t.(!i) <-
[|
(1,[|1 ;1;1|],1.0);
(1,[|1 ;1;1|],1.0);
(1,[|1 ;1;1|],1.0);
(1,[|1 ;1;1|],1.0)
|] );;
There still an error
I use ocamlc now which works well.
Thank you for your advice.
--
Franck Delaplace @w3:http://www.lami.univ-evry.fr/~delapla/ <http://www.lami.univ-evry.fr/%7Edelapla/>
Equipe BioInfo, La.M.I-U.M.R 8042 C.N.R.S
523 Place des Terrasses
91025 Evry CEDEX (France)
[-- Attachment #2.1: Type: text/html, Size: 3203 bytes --]
[-- Attachment #2.2: Drafts --]
[-- Type: image/gif, Size: 144 bytes --]
next prev parent reply other threads:[~2002-03-12 7:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-11 7:51 Franck Delaplace
2002-03-11 12:36 ` M E Leypold @ labnet
2002-03-12 7:30 ` Franck Delaplace [this message]
2002-03-12 9:12 ` Christopher Quinn
2004-09-20 19:27 Tyler Eaves
2004-09-22 15:16 ` Christophe TROESTLER
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=3C8DAE99.9040309@lami.univ-evry.fr \
--to=delapla@lami.univ-evry.fr \
--cc=caml-list@inria.fr \
--cc=leypold@informatik.uni-tuebingen.de \
/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