From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on yquem.inria.fr X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=AWL,HTML_MESSAGE autolearn=disabled version=3.1.3 Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39]) by yquem.inria.fr (Postfix) with ESMTP id 67C44BC69 for ; Fri, 31 Aug 2007 19:03:49 +0200 (CEST) Received: from smtp.janestcapital.com (www.janestcapital.com [66.155.124.107]) by concorde.inria.fr (8.13.6/8.13.6) with ESMTP id l7VH3mDb016385 for ; Fri, 31 Aug 2007 19:03:48 +0200 Received: from [172.25.129.161] [38.96.172.125] by janestcapital.com with ESMTP (SMTPD-9.10) id AA0E06F8; Fri, 31 Aug 2007 13:04:14 -0400 Message-ID: <46D849F2.4050403@janestcapital.com> Date: Fri, 31 Aug 2007 13:03:46 -0400 From: Brian Hurt User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mathias Kende Cc: OCaml List Subject: Re: [Caml-list] int overflow and Marshal failure References: <6cd4x4ae5k.fsf@hod.lan.m-e-leypold.de> <1188577819.7084.21.camel@MATHIAS-ENS> In-Reply-To: <1188577819.7084.21.camel@MATHIAS-ENS> Content-Type: multipart/alternative; boundary="------------030905030900000005040202" X-j-chkmail-Score: MSGID : 46D849F4.000 on concorde : j-chkmail score : X : 0/20 1 0.000 -> 1 X-Miltered: at concorde with ID 46D849F4.000 by Joe's j-chkmail (http://j-chkmail . ensmp . fr)! X-Spam: no; 0.00; 0200,:01 markus:01 integers:01 0200,:01 markus:01 integers:01 mathias:98 mathias:98 wrote:01 wrote:01 unix:01 unix:01 caml-list:01 marshal:01 int:01 X-Attachments: cset="UTF-8" cset="UTF-8" This is a multi-part message in MIME format. --------------030905030900000005040202 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Mathias Kende wrote: >Le jeudi 30 août 2007 à 23:47 +0200, Markus E L a écrit : > > >>A check in the Unix library would be nice, in the long run I think >>using 32bit native integers is absolutely required. >> >> > >I had the same sort of problem with the Unix.stat function and the >st_size member being an int while it is a 64 bits int on recent systems >(including some 32 bits one). The maximum size that can be stored on 32 >bits system, 1Go, is much too small for this function. > > As a side note, this is why I think the x86 should have gone 64-bit a decade ago now (and was saying that then). Apparently, 2G should be enought for anyone. Brian --------------030905030900000005040202 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit Mathias Kende wrote:

Le jeudi 30 août 2007 à 23:47 +0200, Markus E L a écrit :

A check in the Unix library would be nice, in the long run I think
using 32bit native integers is absolutely required.


I had the same sort of problem with the Unix.stat function and the
st_size member being an int while it is a 64 bits int on recent systems
(including some 32 bits one). The maximum size that can be stored on 32
bits system, 1Go, is much too small for this function.

As a side note, this is why I think the x86 should have gone 64-bit a decade ago now (and was saying that then).

Apparently, 2G should be enought for anyone.

Brian

--------------030905030900000005040202--