From: Richard Jones <rich@annexia.org>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Gripes with array
Date: Thu, 9 Sep 2004 09:23:54 +0100 [thread overview]
Message-ID: <20040909082354.GA22512@annexia.org> (raw)
In-Reply-To: <16704.901.571258.566181@gargle.gargle.HOWL>
[-- Attachment #1: Type: text/plain, Size: 1668 bytes --]
On Thu, Sep 09, 2004 at 09:17:25AM +0200, Jean-Christophe Filliatre wrote:
>
> Jon Harrop writes:
> >
> > Does anyone have any pointers to information about the origin of the size
> > limit for arrays? I assume it is something to do with the garbage collector
> > using a fixed-size tag instead of a variable-size one but I'd be interested
> > in the details.
>
> In ocaml sources, the file byterun/mlvalues.h gives all details about
> the block header structure. There you can see that, on 32 bits
> architecture, the block size (in words) is stored on 22 bits. And
> indeed Sys.max_array_length is equal to 2^22-1.
>
> But I must agree with you: this is definitely too small and we could
> imagine that, when the tag says a block is an array, the size is
> stored within the first (or the last) field instead.
I have a similar problem with the maximum size of strings. In
practical terms, it limits the size of file uploads to COCANWIKI to
around 6 MB (ie., not very much) [not the full 16 MB because of
character escaping, but even 16 MB would be far too small].
Does the tag field need to be so wide? What does the tag mean if it
has different values < No_scan_tag (251)?
Agree with the comment about us all migrating to 64 bit architectures
very soon, although I've been waiting to do this since around '92.
Rich.
--
Richard Jones. http://www.annexia.org/ http://www.j-london.com/
Merjis Ltd. http://www.merjis.com/ - improving website return on investment
MOD_CAML lets you run type-safe Objective CAML programs inside the Apache
webserver. http://www.merjis.com/developers/mod_caml/
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-09-09 8:23 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-09 2:10 Jon Harrop
2004-09-09 5:08 ` Ville-Pertti Keinonen
2004-09-09 7:17 ` Jean-Christophe Filliatre
2004-09-09 8:23 ` Richard Jones [this message]
2004-09-09 9:08 ` Olivier Andrieu
2004-09-09 12:08 ` Basile Starynkevitch [local]
2004-09-09 12:31 ` Damien Doligez
2004-09-09 10:42 ` Gerd Stolpmann
2004-09-09 9:37 ` Damien Doligez
2004-09-09 10:34 ` Jean-Christophe Filliatre
2004-09-09 12:15 ` Igor Pechtchanski
2004-09-09 13:01 ` Brian Hurt
2004-09-09 20:08 ` [Caml-list] 32-bit is sticking around Brandon J. Van Every
2004-09-09 21:04 ` Jon Harrop
2004-09-11 15:30 ` Lars Nilsson
2004-09-11 16:24 ` [off topic] " David MENTRE
2004-09-11 17:52 ` Lars Nilsson
[not found] ` <200409111656.11952.jon@jdh30.plus.com>
2004-09-11 17:47 ` Lars Nilsson
2004-09-09 16:58 ` [Caml-list] Gripes with array Jon Harrop
2004-09-10 5:56 ` Array.init (was [Caml-list] Gripes with array) Christophe Raffalli
2004-09-10 8:53 ` Richard Jones
2004-09-10 14:50 ` Damien Doligez
2004-09-13 7:02 ` Christophe Raffalli
2004-09-10 13:45 ` [Caml-list] Gripes with array Damien Doligez
2004-09-11 1:43 ` skaller
2004-09-11 3:16 ` skaller
2004-09-11 14:36 ` Jon Harrop
2004-09-11 20:53 ` Damien Doligez
2004-09-12 15:33 ` Jon Harrop
2004-09-12 16:07 ` Basile Starynkevitch [local]
2004-09-10 23:48 ` brogoff
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=20040909082354.GA22512@annexia.org \
--to=rich@annexia.org \
--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;
as well as URLs for NNTP newsgroup(s).