From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,9a586954b11ae008
X-Google-Attributes: gid103376,public
From: dewar@merv.cs.nyu.edu (Robert Dewar)
Subject: Re: Overflows (lisp fixnum-bignum conversion)
Date: 1997/04/07
Message-ID: <dewar.860424609@merv>#1/1
X-Deja-AN: 231346091
References: <1997Apr2.202514.1843@nosc.mil>
 <Pine.SUN.3.96.970405054237.22894A-100000@eskimo.com>
 <E874Gq.91M@world.std.com> <01bc42b0$a88691c0$90f482c1@xhv46.dial.pipex.com>
 <E89rwE.K6M@world.std.com>
Organization: New York University
Newsgroups: comp.lang.ada
Date: 1997-04-07T00:00:00+00:00
List-Id: <comp.lang.ada>


Bob Duff said

<<(By the way, in going from a 32-bit address to a 64-bit address, don't
think in terms of doubling the size of the address.  In fact, you're
multiplying the the size of the address space by about 4 billion, which
is an awful lot.  Much bigger than the switch from 16 to 32.  It's hard
for me to even imagine how big 2**64 bytes is.)>>

Yes, but this is address space, not actual data in a program, if you start
mappiong entire file systems into virtual memory, you can be surprised how
fast the 64 bits gets eaten up.