[Vm-dev] Pypy-Squeak VM generation news

Adrian Kuhn akuhn at gmx.ch
Thu Oct 25 18:30:52 UTC 2007

Yes, curiosity.  At least for me.
It is to learn how the pypy tool chain works and to learn how a  
Squeak VM works. The first was fully unknown to me, the latter not in  
Regarding the features of the VM that will result from this  
endeavor ... that's open, it has not yet been generated, neither  
benchmarked :)


On 25 Oct 2007, at 19:37 , Joerg Beekmann wrote:

> I am intruiged by what motivated this? Is it curiosity, will it  
> create a
> VM that is better in some way, will it result in a better mechanism  
> for
> creating VMs?
> Joerg
>> -----Original Message-----
>> From: vm-dev-bounces at lists.squeakfoundation.org
>> [mailto:vm-dev-bounces at lists.squeakfoundation.org] On Behalf
>> Of Adrian Kuhn
>> Sent: October 22, 2007 11:43 PM
>> To: Squeak Virtual Machine Development Discussion
>> Subject: Re: [Vm-dev] Pypy-Squeak VM generation news
>> Hi Andreas and Michael,
>> On 22 Oct 2007, at 23:25 , Michael Haupt wrote:
>>>>> My guess is it's "use the PyPy *tool chain* to generate a Squeak
>>>>> VM".
>>>> And what exactly does *that* mean? Rewrite the code generator in
>>>> Python to generate C code from Slang? Rewrite the VM in
>> Python? Use
>>>> PyPy translation tools to generate code from Squeak parse trees?
>>>> There are so many possible ways of "using tools" ...
>>> it means (simplified) rewriting the VM in Python and compiling it
>>> using the PyPy tool chain.
>> more precise, it means writing a Smalltalk bytecode
>> interpreter in RPython and using the PyPy tool chain to
>> generate a VM out of this.

More information about the Vm-dev mailing list