From: Xavier Leroy <xavier.leroy@inria.fr>
To: Neil Inala <inalan@yahoo.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] bytegen.comp_expr error when doing object copying
Date: Wed, 28 Nov 2001 21:15:44 +0100 [thread overview]
Message-ID: <20011128211544.C11698@pauillac.inria.fr> (raw)
In-Reply-To: <20011127170352.63710.qmail@web14609.mail.yahoo.com>; from inalan@yahoo.com on Tue, Nov 27, 2001 at 09:03:52AM -0800
> Perhaps this should go to caml-bugs only, but I thought discussions
> on the list might disambiguate some assumptions I'm making. Also
> I'm not sure it's a bug. In the code below (section 1), everything
> seems to work fine. The code compiles with no problems. In the
> almost-identical code section 2, the compiler emits the following:
>
> v/64
> >> Fatal error: Bytegen.comp_expr: var v_64
> Uncaught exception: Misc.Fatal_error
This is most certainly a bug in the compiler. "Fatal errors" are,
well, just that: internal inconsistencies in the compiler that should
never happen.
We will investigate, but it would have been preferable to submit a bug
report to caml-bugs@inria.fr: these get archived automatically and are
much harder for us to forget about :-)
- Xavier Leroy
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
prev parent reply other threads:[~2001-11-28 20:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-02 17:53 [Caml-list] replay debugger Yoann Padioleau
2001-10-04 12:39 ` Xavier Leroy
2001-11-26 14:51 ` Fergus Henderson
2001-11-26 16:14 ` Xavier Leroy
2001-11-26 18:40 ` [Caml-list] Beware of compare (and Ocaml beaten by Java) Mattias Waldau
2001-11-27 9:21 ` Xavier Leroy
2001-11-27 9:41 ` Mattias Waldau
2001-11-30 9:12 ` Pierre Weis
2001-12-03 21:37 ` Chris Hecker
2001-11-27 17:03 ` [Caml-list] bytegen.comp_expr error when doing object copying Neil Inala
2001-11-28 20:15 ` Xavier Leroy [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=20011128211544.C11698@pauillac.inria.fr \
--to=xavier.leroy@inria.fr \
--cc=caml-list@inria.fr \
--cc=inalan@yahoo.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).