[squeak-dev] Re: 64-bit images (was: The Trunk:
nsuslovi at gmail.com
Fri Nov 9 21:58:53 UTC 2012
That's great to hear about your plans on Squeak experiments with so strong
And could you please shed light on the current OpenQwaq development status?
What are the priorities for current and future research work?
On Fri, Nov 9, 2012 at 4:10 PM, Andreas.Raab <andreas.raab at gmx.de> wrote:
> Hi David -
> This is great, and just in time! I wanted to play around with Squeak on my
> new z820 development workstation featuring some 256GB of Memory (heh, heh)
> and was wondering where I could find the right Image/VM pair. Thanks for
> - Andreas
> David T. Lewis wrote
> > The purpose of this change to the SystemReporter is to allow it to
> > identify the image format and word size (64-bit or 32-bit) of the image
> > file that is currently being run. An example SystemReporter window from
> > a 64-bit image is attached.
> > A 64-bit version of the trunk image can be found here:
> > http://box3.squeak.org/job/Squeak%2064-bit%20image/
> > A 64-bit image is normally created directly from the normal 32-bit image
> > using a SystemTracer. This Smalltalk script illustrates how it is done:
> > http://box3.squeak.org/job/Squeak%2064-bit%20image/ws/TraceTo64.st
> > To run a 64-bit image on Linux, go to http://squeakvm.org/unix/ and
> > install
> > both the "220.127.116.1114 Unix VM" and the "18.104.22.16814 Unix VM for 64-bit
> > images".
> > The /usr/local/bin/squeak script will then invoke the right VM to run
> > your image, either 32- or 64-bit.
> > If you prefer to compile your VM from source, use the source tarball
> > from http://squeakvm.org/unix/ and run the
> > script with the "--image64" option to build a VM for running 64-bit
> > images. Unofficial and unsupported "bleeding edge" tarballs can also be
> > found at http://box3.squeak.org/job/InterpreterVM/
> > Cog VMs are not currently able to run the 64-bit image, although they
> > certainly will do so in the future. For now, a 64-bit image on a standard
> > interpreter VM will be much slower than the "same" 32-bit image on Cog,
> > but will have greater address space and an ability to reach a much larger
> > total image size.
> > Dave
> > On Thu, Nov 08, 2012 at 04:36:15AM +0000,
> > commits at .squeak
> > wrote:
> >> David T. Lewis uploaded a new version of SystemReporter to project The
> >> Trunk:
> >> http://source.squeak.org/trunk/SystemReporter-dtl.20.mcz
> >> ==================== Summary ====================
> >> Name: SystemReporter-dtl.20
> >> Author: dtl
> >> Time: 7 November 2012, 11:35:58.387 pm
> >> UUID: fb07b2ef-d22a-4054-a266-1e94e274f3ef
> >> Ancestors: SystemReporter-cmm.19
> >> Display image format and word size in #reportImage:
> >> =============== Diff against SystemReporter-cmm.19 ===============
> >> Item was changed:
> >> ----- Method: SystemReporter>>reportImage: (in category 'reporting')
> >> -----
> >> reportImage: aStream
> >> self header: 'Image' on: aStream.
> >> aStream
> >> nextPutAll: Smalltalk image imageName; cr;
> >> nextPutAll: SystemVersion current version; cr;
> >> nextPutAll: Smalltalk image lastUpdateString; cr;
> >> + nextPutAll: Smalltalk image currentChangeSetString; cr.
> >> + [ | imageFormat bitsPerWord |
> >> + imageFormat := Smalltalk image imageFormatVersion.
> >> + bitsPerWord := Smalltalk image wordSize * 8.
> >> + aStream nextPutAll: 'Image format ';
> >> + nextPutAll: imageFormat asString;
> >> + nextPutAll: ' (';
> >> + nextPutAll: bitsPerWord asString;
> >> + nextPutAll: ' bit)'; cr]
> >> + on: Warning
> >> + do: ["primitive not present in VM"].
> >> - nextPutAll: Smalltalk image currentChangeSetString; cr
> >> !
> > System Reporter.png (54K)
> > <http://forum.world.st/attachment/4654568/0/System%20Reporter.png>
> View this message in context:
> Sent from the Squeak - Dev mailing list archive at Nabble.com.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Squeak-dev