From: Gabriel Scherer <gabriel.scherer@gmail.com>
To: Daniel de Rauglaudre <daniel.de_rauglaudre@inria.fr>
Cc: Kakadu <kakadu.hafanana@gmail.com>, Caml List <caml-list@inria.fr>
Subject: Re: [Caml-list] OCaml+spacetime crashes during camlp5 compilation
Date: Fri, 17 Feb 2017 20:58:16 -0500 [thread overview]
Message-ID: <CAPFanBEwL+LCTg_e7rR=xg2WSwuySWsoO6Md=Wr_1Ci_E5e7Zg@mail.gmail.com> (raw)
In-Reply-To: <20170218015321.GA22237@yquem.inria.fr>
Note that a similar bug has already been reported for Camlp4:
https://caml.inria.fr/mantis/view.php?id=7435
Camlp4/Camlp5 tend to be demanding in term of compilation (or rather,
they hit code shapes that the compiler does not handle very well), so
changes that make compilation more resource-intensive, such as
Spacetime, can tip over the edge and provoke a failure -- this is not
due to a hard bug on anyone's side.
On Fri, Feb 17, 2017 at 8:53 PM, Daniel de Rauglaudre
<daniel.de_rauglaudre@inria.fr> wrote:
> Hi,
>
> Which version of OCaml and Camlp5? Taken from where? The github
> sources? Or else which site?
>
> On Sat, Feb 18, 2017 at 01:00:31AM +0300, Kakadu wrote:
>> Hey, folks
>>
>> I got a crash during compilation of camlp5. Is it expected to be easy
>> fixable? Or something terrible?
>>
>> Happy hacking,
>> Kakadu
>>
>> ➜ meta git:(master) ✗ OCAMLRUNPARAM="b" ocamlopt.opt -warn-error A -I
>> ../main -I ../boot -I ../lib -I ../ocaml_stuff/4.04.0/utils -c -impl
>> q_MLast.ppo
>> Fatal error: exception Stack overflow
>>
>> ....
>> Called from file "asmcomp/spill.ml", line 160, characters 32-51
>> Called from file "asmcomp/spill.ml", line 160, characters 32-51
>> Called from file "asmcomp/spill.ml", line 160, characters 32-51
>> Called from file "asmcomp/spill.ml", line 160, characters 32-51
>> Called from file "asmcomp/spill.ml", line 173, characters 8-60
>> Called from file "asmcomp/spill.ml", line 160, characters 32-51
>> Called from file "asmcomp/spill.ml", line 160, characters 32-51
>> Called from file "asmcomp/spill.ml", line 160, characters 32-51
>> Called from file "asmcomp/spill.ml", line 160, characters 32-51
>> ....
>>
>> --
>> Caml-list mailing list. Subscription management and archives:
>> https://sympa.inria.fr/sympa/arc/caml-list
>> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
>> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
> --
> Daniel de Rauglaudre
> http://pauillac.inria.fr/~ddr/
>
> --
> Caml-list mailing list. Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
next prev parent reply other threads:[~2017-02-18 1:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-17 22:00 Kakadu
2017-02-18 1:53 ` Daniel de Rauglaudre
2017-02-18 1:58 ` Gabriel Scherer [this message]
2017-02-18 7:39 ` Kakadu
2017-02-18 8:49 ` Leo White
2017-02-18 10:31 ` Daniel de Rauglaudre
2017-02-18 11:17 ` Kakadu
2017-02-18 20:52 ` Gerd Stolpmann
2017-02-18 21:02 ` Kakadu
2017-02-18 21:14 ` Kakadu
2017-02-19 3:00 ` Daniel de Rauglaudre
2017-02-19 7:34 ` Kakadu
2017-02-19 8:43 ` Daniel de Rauglaudre
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='CAPFanBEwL+LCTg_e7rR=xg2WSwuySWsoO6Md=Wr_1Ci_E5e7Zg@mail.gmail.com' \
--to=gabriel.scherer@gmail.com \
--cc=caml-list@inria.fr \
--cc=daniel.de_rauglaudre@inria.fr \
--cc=kakadu.hafanana@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