From: Jon Harrop <jon@ffconsultancy.com>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Caml on intel-OSX
Date: Sat, 11 Jun 2005 00:39:17 +0100 [thread overview]
Message-ID: <200506110039.18279.jon@ffconsultancy.com> (raw)
In-Reply-To: <1118357500.8693.80.camel@rosella.wigram>
On Thursday 09 June 2005 23:51, John Skaller wrote:
> Whilst I personally prefer the ocaml native code compiler,
> at present I can't use it on my AMD64 as there appears
> to be a code generation bug in it for that platform --
Yipes! I'm about to release some commercial software for x86 and AMD64 and I
really didn't want to hear this!
I've been experiencing segfaults on all platforms but I think this is a bug in
lablGL rather than ocamlopt.
Do you think I shouldn't release for AMD64? How confident are you that this is
a codegen bug? Does your code use only OCaml's theoretically safe subset?
--
Dr Jon D Harrop, Flying Frog Consultancy Ltd.
Objective CAML for Scientists
http://www.ffconsultancy.com/products/ocaml_for_scientists
next prev parent reply other threads:[~2005-06-10 23:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-09 5:33 John Skaller
2005-06-09 8:23 ` [Caml-list] " Agustín Valverde
2005-06-09 14:00 ` james woodyatt
2005-06-09 15:27 ` John Skaller
2005-06-09 16:20 ` padiolea
2005-06-09 22:51 ` John Skaller
2005-06-10 0:02 ` Jonathan Bryant
2005-06-10 2:55 ` John Skaller
2005-06-10 7:10 ` Florian Hars
2005-06-10 0:41 ` Jacques Garrigue
2005-06-10 1:57 ` John Skaller
2005-06-14 0:28 ` Sven Luther
2005-06-10 6:35 ` Stefano Zacchiroli
2005-06-10 9:07 ` John Skaller
2005-06-10 23:39 ` Jon Harrop [this message]
2005-06-11 18:39 ` John Skaller
2005-06-11 19:03 ` Jon Harrop
2005-06-12 6:58 ` John Skaller
2005-06-13 19:19 ` [Caml-list] AMD64 ocamlopt bug Xavier Leroy
2005-06-13 19:32 ` John Skaller
2005-06-13 20:18 ` Damien Doligez
2005-06-13 20:27 ` John Skaller
2005-06-13 21:01 ` Anil Madhavapeddy
2005-06-09 23:44 ` [Caml-list] Caml on intel-OSX Jonathan Bryant
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=200506110039.18279.jon@ffconsultancy.com \
--to=jon@ffconsultancy.com \
--cc=caml-list@yquem.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;
as well as URLs for NNTP newsgroup(s).