Hi All!
I have reached step 2.4 in my SqueakElib plan documented here:
http://wiki.squeak.org/squeak/6011, but I don't know anything about Exupery.
I suppose my first question is whether I am right in assuming that I will
see speedups if I incorporate Exupery?
My next question is related to the work I did in steps 1.3, 1.4, and 1.5. I
modified the VM to use larger contexts (80+7), to add extra long jump
bytecodes for jump:, jumpIfTrue: and jumpIfFalse:, and to add bytecodes for
doing receiver class tests. Will these additions cause problems with
Exupery?
If all is ok so far, I want to build my modified Windows VM with Exupery, so
I am reading http://wiki.squeak.org/squeak/5904. I am confused as to which
VMMaker I can use to build. I currently have VMMaker-tpr.58.mcz loaded.
Can you confirm that I need to either overwrite this VMMaker with the one
from the Exupery repository or that I need to build fresh with the one from
the Exupery repository? Also, where is the VMMaker from the Exupery
repository - where is the Exupery repository? Finally, what is the best
Subversion client for Windows and how do I connect to this Exupery
repository?
Thanks and Cheers,
Rob
This release
* Has a background compiler that can be run for about a hour
* Has many bug fixes
* Merges in David and John's 32 bit clean work and makes Exupery
32 bit clean.
Installation instructions and links to VM's and pre-built images
are here:
http://wiki.squeak.org/squeak/3945
To use the background compiler:
First initialise Exupery to prepare the code cache. This will
also clear out any currently compiled code.
Exupery initialiseExupery
Then start the background compiler using the following expression.
Exupery startBackgroundCompilation.
Then when done use the following to stop it.
Exupery stopBackgroundCompilation.
Thanks to Andy Tweek and Mathieu Suen for building the
Windows and Mac VMs.
The Mac VM was built with gcc optimisation switched off to
avoid a bug in gcc 4.0 so it's probably much slower than the
normal VM.
This is still an alpha release, running the background compiler will
lead to crashes, but it should run for long enough to play with. The
next release will improve both the profiler that drives background
compilation and reliability.
Bryce