[Vm-dev] VM Maker: VMMaker.oscog-eem.276.mcz

Frank Shearar frank.shearar at gmail.com
Wed May 22 07:57:45 UTC 2013


On 21 May 2013 23:29, Eliot Miranda <eliot.miranda at gmail.com> wrote:
>
>
>
> On Tue, May 21, 2013 at 3:27 PM, Eliot Miranda <eliot.miranda at gmail.com> wrote:
>>
>> Hi Frank,
>>
>>
>> On Sat, May 18, 2013 at 3:34 PM, Frank Shearar <frank.shearar at gmail.com> wrote:
>>>
>>>
>>> On 21 March 2013 23:44,  <commits at source.squeak.org> wrote:
>>> >
>>> > Eliot Miranda uploaded a new version of VMMaker to project VM Maker:
>>> > http://source.squeak.org/VMMaker/VMMaker.oscog-eem.276.mcz
>>> >
>>> > ==================== Summary ====================
>>> >
>>> > Name: VMMaker.oscog-eem.276
>>> > Author: eem
>>> > Time: 21 March 2013, 4:43:39.056 pm
>>> > UUID: 52d03a8f-11ec-4454-9c4a-ea1c383f339a
>>> > Ancestors: VMMaker.oscog-eem.275
>>> >
>>> > Cogit:
>>> > Stop reporting EncounteredUnknownBytecode with an error message.
>>> >
>>> > Fix slip in ceSICMiss: that didn't link new PIC if an MNU case.
>>> >
>>> > Better document the calling conventions.
>>> >
>>> > Add an assert to genGetImplicitReceiverFor:forPush: that checks
>>> > the appropriate use of the IsNSSend annotation.
>>> >
>>> > Fix simulation bug in CogMethodSurrogate>>nextOpenPIC.
>>> >
>>> > Slang:
>>> > Nuke unused InterpreterSimulationObject.
>>> >
>>> > =============== Diff against VMMaker.oscog-eem.275 ===============
>>>
>>> I realise I've just reported a Cog build failure, but when might we
>>> see the unusedBytecode stuff land in a released VM? I'd love to play
>>> with MethodMassage, without having to custom build a Cog. (Although I
>>> suspect I could do just that for the moment...)
>>>
>>> frank
>>
>>
>> I think the latest version on the site, r2714, does support this.  See http://www.mirandabanda.org/files/Cog/VM/VM.r2714/ChangeHistory, or am I confused?
>
>
> Uh, I'm confused ;)  I'll try and do an up-to-date build before the end of the week.

Yeah, I read "bad things could happen if the VM doesn't support this",
thought "what could possibly go wrong?!", ran the tests and saw the VM
bail hard :)

frank

> --
> doh!
> Eliot
>


More information about the Vm-dev mailing list