2014-05-19 20:50 GMT+02:00 <[hidden email]>: Or are these things still usefull for some boostrap voodoo?Eliot Miranda uploaded a new version of Kernel to project The Trunk: Note that this change makes ClosureCompilerTest>>#testSourceRangeAccessForBlueBookInjectInto fail But the test itself is for pre-closure byteCodes (using EncoderForV3, or so called Blue Book blocks with blockCopy byteCode) In my image, I have no blue book CompiledMethod, if I believe this snippet: CompiledMethod allInstances count: [:e | ((InstructionStream on: e) scanFor: [:instr | instr = 200]) or: [(e hasLiteral: #blockCopy:) and: [e messages includes: #blockCopy:]]]. Do we really want to support this old thing?
Or is there a danger that some old ImageSegment bring some zombies back? Or shall we remove this test and support of previous bytecode set (EncoderForV3)? Currently, debugging such compiled method fails with sticky debuggers... Some bytes are rotting, we lack tests, a single person is active/fluent on this part, so dropping support is a reasonnable option. |
Free forum by Nabble | Edit this page |