On 02 Jul 2014, at 16:59, Eliot Miranda <eliot.mira...@gmail.com> wrote:

> Hi Esteban, Hi Guille,
> 
> 
> On Wed, Jul 2, 2014 at 7:56 AM, Esteban Lorenzano <esteba...@gmail.com> wrote:
> 
> On 02 Jul 2014, at 16:43, Denis Kudriashov <dionisi...@gmail.com> wrote:
> 
>> Great!
>> 
>> How you built Pharo image for Spur?
>> I read from Eliot mails that for Squeak he has something like 'Sput 
>> bootstrap: 'some.image'. 
>> Do you implement something similar? If yes then why converting Pharo3 images 
>> will not work?
> 
> we adapted same bootstrap
> it will not work for pharo3 because we need to add some classes, modify some 
> others and reload the old class builder to bootstrap (and the new class 
> builder needs to be fundamentally modified). 
> so is a lot of work, and does not corresponds to a stable version. 
> also, Spur will be stable some months from now… so it has sense to make it 
> for pharo4 and not for older versions. 
> 
> Great news!  Can you send me change sets so I can integrate into 
> VMMaker.oscog?

Not yet… it is still very dirty. 
For now I’m going to the green as fast as I can and I will clean later :P

>  
> 
> Esteban 
> 
>> 
>> Best regards,
>> Denis
>> 
>> 
>> 2014-07-02 18:13 GMT+04:00 Esteban Lorenzano <esteba...@gmail.com>:
>> Hi,
>> 
>> I’ve been working on prepare Pharo to run with the new Spur VM… and finally 
>> this week Guille and I sit together and make a huge advance :)
>> here a screenshot of pharo 4 running with spur: 
>> <Screen Shot 2014-07-02 at 15.58.17.png>
>> for more information, same image before migration, with a regular cogvm 
>> gives this numbers: '1297023432 bytecodes/sec; 161029354 sends/sec’, so that 
>> means that the tiny benchmarks run at 166% the speed of the old vm… 
>> Of course this is just one benchmark, but I’m very impressed :)
>>  
>> Now, it is still not usable but I’m confident I can put a jenkins job to 
>> work very soon :)
>> 
>> Esteban
>> 
>> ps: before you start asking: Spur WILL NOT be available for Pharo3, it will 
>> be part of Pharo4. 
>> 
>> 
>> 
>> 
> 
> 
> 
> 
> -- 
> best,
> Eliot

Reply via email to