[Vm-dev] Re: [Pharo-project] squeak VM 5.0
David T. Lewis
lewis at mail.msen.com
Sat Dec 5 18:54:47 UTC 2009
Hi,
(cc to vm-dev list)
The 64-bit image that I provided is a direct descendent of the original
one that was produced by Dan and Ian.
Original 64-bit image:
http://squeakvm.org/squeak64/dist3/Squeak64-3.8g-6548.image.tar.gz
My update:
http://squeakvm.org/squeak64/sq64-dtl.zip
The original one was produced with a specialized system tracer, the code
for which is here:
http://squeakvm.org/squeak64/dist3/ChangeSets/System-Tracing.2.cs
I did *not* use the system tracer to produce the updated image. Instead,
it is the original image with various updates that I made over the years to
keep up with VM developments (which were not entirely backward compatible).
The original image will not run on a current VM, and that is the reason
that I posted my update.
The system tracer (including the specialized 64-bit one) does not work
on little-endian machines. Somebody (tm) should fix this one of these
days. There are a couple of Mantis reports related to this:
http://bugs.squeak.org/view.php?id=5240
http://bugs.squeak.org/view.php?id=5239
As far as producing a 64-bit Pharo image, I think there are two things
that could be tried:
1) Fix the system tracer to work on little-endian boxes (probably
not too difficult), then try tracing some Pharo and Squeak images
into 64-bit format.
2) Find somebody who has a big-endian Mac available, and have them
try tracing some images.
I can think of no reason why the newer images with closure support
could not be traced into 64-bit formats, but I guess the only way to
find out is to try it and see what happens.
Dave
On Fri, Dec 04, 2009 at 01:39:28PM -0800, John M McIntosh wrote:
> I think David Lewis made the last one, let's cc him.
>
> Perhaps the process would be
>
> Examine the squeak image.
> take the required source that does the system tracing
> someone make a MC project (no idea if one exists?)
>
> a) file that into a Pharo image.
> b) Correct things like references to Smalltalk, versus SmalltalkImage current
> c) run it.
> d) place 64bit image on pharo server.
>
> I note to run the system tracer you need to run it either on a PowerPC.
> Or on a MacIntel using a 4.x series macintosh VM, make a copy, do a get info on the VM
> check "Open using Rosetta"
>
> If "Open using Rosetta" is not an option and you are running 10.6 then it is likely you did
> not install Rosetta when you upgraded/installed 10.6. You need to find your 10.6 DVD
> and lookup how to install Rosetta after installing 10.6
>
> PS yes you could use a 10.5 series VM for this too.
>
>
> However to complicate things I don't think anyone has done a Closure based image
> and I don't know if that will be a problem. You could take a pre-closure Pharo image
> and try it just to get past the point where having the SystemTracer code in a MC is done.
>
>
> On 2009-12-04, at 1:23 PM, Laval Jannik wrote:
>
> > Hi Alex,
> >
> > PharoCore is a 32bits image.
> > So it works on Squeak.5.0.0.b9.64*32.app.
> >
> > I see that Squeak has a 64bits fork image, is it possible to have a Pharo one?
> > What is the process to do this ?
> >
> > Cheers,
> > Jannik
> >
More information about the Vm-dev
mailing list