Version française
Home     About     Download     Resources     Contact us    

This site is updated infrequently. For up-to-date information, please visit the new OCaml website at

Browse thread
Array 4 MB size limit
[ Home ] [ Index: by date | by threads ]
[ Search: ]

[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: -- (:)
From: Oliver Bandel <oliver@f...>
Subject: Re: [Caml-list] Array 4 MB size limit
On Sat, May 20, 2006 at 12:51:08PM +0200, Jozef Kosoru wrote:
> On Fri, May 19, 2006 at 20:57:35 -0400, Brian Hurt wrote:
> > >Yes. 32-bit x86 platform is not going away anytime soon. Given that
> > >512M RAM is now standard and 1G RAM is very common for an average PC
> > 
> > This is what boggles my imagination.  The combination of obstinate
> > adherence to a limited platform (x86-32) in the same breath as a
> > recognition that we are approaching the limitations of that
> > architecture.  It's the 640K limit all over again.
> > 
> > And no, segments will not help the situation.  Every single process is
> > limited to 4G of address space, period.  Read the Intel CPU docs.
> > With reasonable amounts of virtual memory we're well above that
> > already- and we're approaching that with real memory.
> 4G address space limit is off-topic here. Please note that the OCaml
> array size limit is 4M not 4G.
> > Now, I realize the core reasons for the delay in moving to 64-bits are
> > industry wide.  Intel's Itanium fiasco delayed Intel introducing a
> > 64-bit chip at least 7 years.  And Microsoft seems to be incapable of
> > releasing a new OS- 32-bit or 64-bit.  But that, I think, is the core
> > of the problem- Ocaml's array limit is just one of many symptoms.
> > 
> > And that's my point- we should be looking to fix the underlying
> > problem, not looking to patch the symptoms.  Because often times
> > patching the symptoms and not addressing the core problem simply makes
> > the whole situation worse- the underlying problem simply shows up in
> > new ways, and the fix for the specific symptom often causes new
> > problems.
> I disagree. Actually I think an opposite. A suggestion to move to 64-bit
> is just patching the symptoms of the real problem - a design flaw in the
> OCaml programming language.


It would be a design flaw when future processors would make bigger problems.
You may have missed the historical note from Xavier: OCaml is a BACK-port.

What kind of problems would you run into, when backporting your current
applications to a 16 or 8 Bit processor?
Would you call that breaking code degned by flaw?

The year 2k problem we have left behind, but the POSIX timer (derived
from the Unix time) will overflow in 2038.

So, he have some years to switch to 64 Bit platforms,
before the year 2038 problem will make trouble ;-)