[Pharo-dev] Stack size for compiled methods (issue 13854 Crash/hang on array access)

Hi, on what depends the stack size for a compiled method? I try to figure out, why the old compiler and the opal compile generate different compiled method headers. I think this comes from a wrong stack size computed by opal, but I can not figure out how the stack size is computed. Old Compiler PolygonMorph>>#lineSegmentsDo: header -> "primitive: 0 numArgs: 1 numTemps: 3 numLiterals: 23 frameSize: 56" Opal compiler: PolygonMorph>>#lineSegmentsDo: header -> "primitive: 0 numArgs: 1 numTemps: 3 numLiterals: 23 frameSize: 16"