On Tue, Feb 5, 2013 at 1:21 PM, Camillo Bruni <[email protected]>wrote:
> > On 2013-02-05, at 22:15, Eliot Miranda <[email protected]> wrote: > > > On Tue, Feb 5, 2013 at 1:12 PM, Camillo Bruni <[email protected] > >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." > > nope it is NOT the cog VM, your branch doesn't have a set of changes we > made, > notably to the file plugins, furthermore we ship by default with the native > boost plugin. > > so to be fully correct I have to say *former*. > No. Cog is an architecture, a JIT plus an Interpreter, not a specific VM. StackVM is an architecture. Interpreter VM is an architecture. You could clarify by saying "The Pharo VM (a derivative of the Cog VM) ..." or "The Pharo VM (a version of the Cog VM) ..." -- best, Eliot
