Dave Lewis uploaded a new version of VMMaker to project VM Maker:
http://www.squeaksource.com/VMMaker/VMMaker-dtl.205.mcz==================== Summary ====================
Name: VMMaker-dtl.205
Author: dtl
Time: 23 November 2010, 11:48:05 am
UUID: f23a18c7-ad62-4a4e-8f92-9b6b02cd9e3a
Ancestors: VMMaker-dtl.204
VMMaker 4.3.18
Adopt #isOopCompiledMethod: from oscog and update accordingly:
Interpreter>>primitiveClosureValue
Interpreter>>primitiveClosureValueNoContextSwitch
Interpreter>>primitiveClosureValueWithArgs
Merge isOopCompiledMethod: call into #primitiveExecuteMethodArgsArray (VMMaker version has 64 bit changes not applicable to oscog).
Use is#OopCompiledMethod: idiom in Interpreter>>lookupMethodInDictionary:
Merge #primitivePerform and #primitivePerformAt. This adds checks for SmallInteger as as method missing from the previous update (allow foo perform: #bar where bar is a SmallInteger in the method cache).
Question: #primitivePerform and #primitivePerformAt in oscog call #executeNewMethod rather than #executeNewMethodFromCache. Should this be applied to VMMaker? I did not understand the implications so did not make the update.
Eliot: The Interpreter>>lookupMethodInDictionary: update should be added to the oscog branch.
Locked
