From: Gabriel Scherer <gabriel.scherer@gmail.com>
To: "A. Moo" <moosotc@gmail.com>
Cc: caml <caml-list@inria.fr>
Subject: Re: [Caml-list] Native compiler liveness failure
Date: Fri, 10 Mar 2017 12:04:16 -0500 [thread overview]
Message-ID: <CAPFanBEgkqq9t7XjX4s+a7aPE7QnwthTLZMF+eDNDtG-8iszaw@mail.gmail.com> (raw)
In-Reply-To: <87tw71ulal.fsf@gmail.com>
Could you write a bug report on the Mantis bugtracker:
https://caml.inria.fr/mantis/
?
I am not sure what you mean by "not being sure how to fill a proper
bug report". When in doubt about how to file (but you really think
it's a bug), I would think that a Mantis report is better than a
caml-list post, because it's easy to change Mantis bug details after
the fact.
(The people that watch the bugtracker also watch the caml-list, so
that means that posting to caml-list about bugs risks sending
not-so-relevant messages to strictly more people.)
(Another option is to send a message on the relevant Github PR if you
have identified the PR responsible for merging the breaking change in
trunk. When in doubt, the mantis entry is a safe choice.)
If you have questions about how to file the actual report, I would be
happy to give more information -- send me an email. The summary is
that this is in the "backend" category, and that the product version
should be the latest development branch (if you use "trunk"), that is
currently 4.06+0+dev.
On Fri, Mar 10, 2017 at 11:52 AM, <moosotc@gmail.com> wrote:
>
> Not being sure how to fill a proper bug report in this case posting the
> problem description here.
>
> When trying to build llpp [1] with native code ocaml compiler (git
> 9e81b0fb4be4a2dc9114efb630fea192c7d04e1e) I'm getting a compiler error:
>
> ocamlopt -c -I ./lablGL -I build-ocaml-git/lablGL -I build-ocaml-git -I build-ocaml-git/wsi/x11 -o build-ocaml-git/main.cmx ./main.ml
> File "_none_", line 1:
> Warning 58: no cmx file was found in path for module Wsi, and its interface was not compiled with -opaque
> spilled-cmd/75
>>> Fatal error: Liveness.fundecl
> Fatal error: exception Misc.Fatal_error
> Raised at file "utils/misc.ml", line 21, characters 54-71
> Called from file "asmcomp/asmgen.ml" (inlined), line 31, characters 2-29
> Called from file "asmcomp/asmgen.ml", line 118, characters 46-60
> Called from file "utils/misc.ml", line 28, characters 20-27
> Re-raised at file "utils/misc.ml", line 28, characters 50-57
> Called from file "asmcomp/asmgen.ml" (inlined), line 102, characters 15-18
> Called from file "asmcomp/asmgen.ml", line 107, characters 2-659
> Called from file "list.ml", line 100, characters 12-15
> Called from file "utils/misc.ml", line 28, characters 20-27
> Re-raised at file "utils/misc.ml", line 28, characters 50-57
> Called from file "asmcomp/asmgen.ml" (inlined), line 102, characters 15-18
> Called from file "asmcomp/asmgen.ml", line 179, characters 2-118
> Called from file "asmcomp/asmgen.ml", line 154, characters 6-12
> Re-raised at file "asmcomp/asmgen.ml", line 159, characters 6-15
> Re-raised at file "asmcomp/asmgen.ml", line 170, characters 4-13
> Called from file "driver/optcompile.ml" (inlined), line 67, characters 15-18
> Called from file "driver/optcompile.ml", line 127, characters 16-303
> Called from file "utils/misc.ml", line 28, characters 20-27
> Re-raised at file "utils/misc.ml", line 28, characters 50-57
> Called from file "driver/optcompile.ml" (inlined), line 67, characters 15-18
> Called from file "driver/optcompile.ml", line 121, characters 10-622
> Called from file "driver/optcompile.ml", line 139, characters 8-68
> Re-raised at file "driver/optcompile.ml", line 144, characters 6-13
> Called from file "utils/misc.ml", line 28, characters 20-27
> Re-raised at file "utils/misc.ml", line 28, characters 50-57
> Called from file "driver/compenv.ml", line 561, characters 6-35
> Called from file "list.ml", line 100, characters 12-15
> Called from file "driver/compenv.ml", line 637, characters 2-61
> Called from file "driver/optmain.ml", line 246, characters 6-164
> Re-raised at file "parsing/location.ml", line 456, characters 14-25
> Re-raised at file "parsing/location.ml", line 456, characters 14-25
> Re-raised at file "parsing/location.ml", line 456, characters 14-25
>
> Build command lines that produced this partiuclar ocamlopt invocation was:
>
> OCAMLRUNPARAM=b PATH=/home/malc/tmp/ocaml-git/bin:$PATH native=yes sh -x build.sh build-ocaml-git
>
> [1] https://github.com/moosotc/llpp/
> | http://repo.or.cz/w/llpp.git
>
> --
> mailto:moosotc@gmail.com
>
> --
> 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
prev parent reply other threads:[~2017-03-10 17:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-10 16:52 moosotc
2017-03-10 16:59 ` Mark Shinwell
2017-03-10 17:02 ` Mark Shinwell
2017-03-10 17:21 ` moosotc
2017-03-10 17:31 ` Mark Shinwell
2017-03-10 17:04 ` Gabriel Scherer [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=CAPFanBEgkqq9t7XjX4s+a7aPE7QnwthTLZMF+eDNDtG-8iszaw@mail.gmail.com \
--to=gabriel.scherer@gmail.com \
--cc=caml-list@inria.fr \
--cc=moosotc@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;
as well as URLs for NNTP newsgroup(s).