From: "Kevin Lang" <Kevin.Lang@Overture.com>
To: <caml-list@inria.fr>
Subject: [Caml-list] opteron query + whining about array size limit
Date: Fri, 13 Jun 2003 13:36:34 -0700 [thread overview]
Message-ID: <A1D15F63E02DC042B83290F953737F1D065978C0@PASEXCHG-1.Search.Corpsys.P4pnet.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 561 bytes --]
Is an Opteron backend for ocamlopt in the works?
Given that we deal with very large graphs here at
Overture (an internet search company), I have been
frustrated by Ocaml's 2^22 maximum dimension for
native arrays on a 32-bit machine.
I tried using our 64-bit Itanium, but it is 10 times
slower than our 32-bit Intel machines, so I have stuck
with the latter using ugly workarounds like 2-level native
arrays and bigarrays of integer indexes.
BTW, we don't actually have an Opteron box yet, but it is
quite likely that we will be getting one.
[-- Attachment #2: Type: text/html, Size: 1005 bytes --]
next reply other threads:[~2003-06-13 20:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-13 20:36 Kevin Lang [this message]
2003-06-14 12:41 ` Xavier Leroy
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=A1D15F63E02DC042B83290F953737F1D065978C0@PASEXCHG-1.Search.Corpsys.P4pnet.net \
--to=kevin.lang@overture.com \
--cc=caml-list@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