From xemacs-m  Sat Jun 21 03:25:36 1997
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by xemacs.org (8.8.5/8.8.5) with SMTP id DAA17997
	for <xemacs-beta@xemacs.org>; Sat, 21 Jun 1997 03:25:36 -0500 (CDT)
Received: from Eng.Sun.COM ([129.146.1.25]) by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id BAA08658; Sat, 21 Jun 1997 01:47:28 -0700
Received: from kindra.eng.sun.com by Eng.Sun.COM (SMI-8.6/SMI-5.3)
	id BAA09156; Sat, 21 Jun 1997 01:25:07 -0700
Received: from xemacs.eng.sun.com by kindra.eng.sun.com (SMI-8.6/SMI-SVR4)
	id BAA13220; Sat, 21 Jun 1997 01:25:05 -0700
Received: by xemacs.eng.sun.com (SMI-8.6/SMI-SVR4)
	id BAA07607; Sat, 21 Jun 1997 01:25:04 -0700
Date: Sat, 21 Jun 1997 01:25:04 -0700
Message-Id: <199706210825.BAA07607@xemacs.eng.sun.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
From: Martin Buchholz <mrb@Eng.Sun.COM>
To: Kyle Jones <kyle_jones@wonderworks.com>
Cc: XEmacs Beta Test <xemacs-beta@xemacs.org>
Subject: Yet more 64bits lossage
In-Reply-To: <QQcuvx10888.199706210628@crystal.WonderWorks.COM>
References: <19970621012424.18989@iria.mines.u-nancy.fr>
	<199706210604.XAA07502@xemacs.eng.sun.com>
	<QQcuvx10888.199706210628@crystal.WonderWorks.COM>
X-Mailer: VM 6.32 under 20.3 "Oslo" XEmacs Lucid (beta7)
Reply-To: Martin Buchholz <mrb@Eng.Sun.COM>

>>>>> "Kyle" == Kyle Jones <kyle_jones@wonderworks.com> writes:

Kyle> Does compiling with 64-bit pointers buy the user anything but
Kyle> trouble?  I'm sure it will give us a warm fuzzy feeling to have it
Kyle> work, but there are icebergs ahead.  If the cause of these crashes
Kyle> is 32-bit ints and 64-bit pointers, then there is the problem that
Kyle> Lisp_Objects are ints.  Any pointer to an object that needs the
Kyle> topmost 64 bits isn't going to fit in a Lisp_Object.  XEmacs is
Kyle> going to go boom if something tries to cram a 64-bit wide pointer
Kyle> in there.  So if XEmacs can't use 64-bit pointers why compile with
Kyle> them?  (I'm assuming the person doing the build has a choice.)

So XEmacs can use more than 256 MB of virtual memory?

This works on an Alpha.

(The top 4 bits of the Lisp_Object are usurped).

The real test is whether a file > 256 MB in size can be edited in
XEmacs.  I've never done this.

Martin

