On Tue, Feb 5, 2013 at 1:12 PM, Camillo Bruni <camillobruni@gmail.com> wrote:

done:
https://ci.inria.fr/pharo/view/VM/job/StackVM/
https://ci.inria.fr/pharo/view/VM/job/PharoVM/

"The Pharo VM (former Cog VM) is a VM that optimizes execution by mapping contexts to stack frames and lazily instantiating contexts.

It further jits/compiles methods used more than once to machine-code and implements a number of send optimization schemes in that machine-code."

=>

"The Pharo VM (also known as the Cog VM) is a VM that optimizes execution by mapping contexts to stack frames and lazily instantiating contexts.

It further jits/compiles methods used more than once to machine-code and implements a number of send optimization schemes in that machine-code."

please.

On 2013-02-05, at 22:09, Camillo Bruni <camillobruni@gmail.com> wrote:

> doing that right now!
>
> On 2013-02-05, at 22:08, Francois Stephany <tulipe.moutarde@gmail.com> wrote:
>> On 05/02/13 21:15, Eliot Miranda wrote:
>>
>>>
>>> No. �The StackVM is a VM that optimizes interpreted execution by mapping
>>> contexts to stack frames and lazily instantiating contexts, but is still
>>> a pure interpreter. �The Cog VM is a VM that optimizes execution
>>> by mapping contexts to stack frames and lazily instantiating contexts,
>>> /and/ by compiling methods used more than once to machine-code and
>>> implementing a number of send optimization schemes in that machine-code.
>>>
>>
>> This could be added in the Jenkins job description!
>>
>

--
best,

Eliot