Loading in a Moose image VMMaker.oscog-eem.240.mcz VMMaker.oscog-eem.236.mcz VMMaker-oscog-LaurentLaffont.303.mcz
There are 12 methods that changed from 236 to 240 that are not the same in 303 (ignoring removed methods): StackInterpreter>findClassOfMethod:forReceiver: StackInterpreter>floatValueOf: ObjectMemory>changeClassOf:to: Cogit>declareCVarsIn: StackInterpreter>isLiveContext: InterpreterPrimitives>isInstanceOfClassByteString: StackInterpreter>longPrintoop: NewObjectMemory>okayOop: NewObjectMemory>incrementalGC:
Stephan
2014-04-02 11:42 GMT+02:00 Stephan Eggermont stephan@stack.nl:
Loading in a Moose image VMMaker.oscog-eem.240.mcz VMMaker.oscog-eem.236.mcz VMMaker-oscog-LaurentLaffont.303.mcz
There are 12 methods that changed from 236 to 240 that are not the same in 303 (ignoring removed methods): StackInterpreter>findClassOfMethod:forReceiver: StackInterpreter>floatValueOf: ObjectMemory>changeClassOf:to: Cogit>declareCVarsIn: StackInterpreter>isLiveContext: InterpreterPrimitives>isInstanceOfClassByteString: StackInterpreter>longPrintoop: NewObjectMemory>okayOop: NewObjectMemory>incrementalGC:
Stephan
Hmm, don't waste too much time. All these methods are unchanged in github pharo-vm head revision (VMMaker-oscog-StefanMarr.313) The cause must be completely different in latest pharo vms.
There are way too many changes to analyze if you want to diff with VMMaker.oscog branch - changes related to using FileSystem instead of FileDirectory - changes related to ephemerons - changes related to NB - ... ? - many many false changes ( just formatting of methods - please don't do that! )
The right way to debug this is to have a VMSimulator working and be patient...
vm-dev@lists.squeakfoundation.org