[Pharo-project] Exupery's VMMaker on SqueakSource now has closures
I can supply a built VM if anyone wants to try it immediately. If not I'll package one up after finishing tidying up. Looking at the bytecodes, they're suppressing context recycling whenever a closure is created. The only reason that closures refer to their surrounding contexts is to support ^ returns from blocks. With two more context creation bytecodes we should allow all contexts to be recycled except the outer method context when there's a block that ^ returns. Such optimisation can wait though, especially as it would involve removing some of Eliot's sanity checking which may be useful when adapting the image to use these bytecodes. Bryce
bryce@kampjes.demon.co.uk schrieb:
I can supply a built VM if anyone wants to try it immediately. If not I'll package one up after finishing tidying up.
Hello Bryce, I'd like to try it out immediately. But... What are the premises? Do I have to build a special VM for Exupery (your post indicates that)? Is Exupery x86_64 compatible? Do I have to take special actions with my image? Can I run 'seaside' with exupery? Are there drawbacks/ gains on memory/ cpu consumption?
Markus Fritsche writes:
bryce@kampjes.demon.co.uk schrieb:
I can supply a built VM if anyone wants to try it immediately. If not I'll package one up after finishing tidying up.
Hello Bryce,
I'd like to try it out immediately. But...
What are the premises? Do I have to build a special VM for Exupery (your post indicates that)? Is Exupery x86_64 compatible? Do I have to take special actions with my image? Can I run 'seaside' with exupery? Are there drawbacks/ gains on memory/ cpu consumption?
I'll bundle up the VM after work. (Tonight UK time) Exupery requires a few VM extensions, they're completely harmless unless you also load Exupery and start it running. I already need to maintain a VM for Exupery, so I merged the changes Pharo wanted into it. By merging the changes into Exupery's branch of VMMaker, they'll get in all future VMs I build. So long as you don't run Exupery, it's just another VM, but with both the truetype font changes and the closure bytecodes. You can run Seaside, and anything else. Exupery itself is compatable with Seaside. There's a tiny fix to Seaside's continuations that's been included in 2.9 that you may want. The VM is a 32 bit one, but runs OK on 64 bit Linux in compatability mode. If you want to have a modern VM with closure bytecodes then using the Exupery VMMaker is a reasonable thing to do. By just building using Exupery's latest version of VMMaker rather than the one from SqueakMap, you'll get closure support and sub-pixel anti-aliasing. Bryce
participants (2)
-
bryce＠kampjes.demon.co.uk -
Markus Fritsche