Leopold Toetsch <[EMAIL PROTECTED]> writes: > Aaron Sherman <[EMAIL PROTECTED]> wrote: >> On Fri, 2004-04-16 at 18:18, Leopold Toetsch wrote: > >> Sorry, I gave the wrong impression. I meant it looks suspiciously like >> Python is doing a lazy construction on those objects, not that there is >> anything wrong with the benchmark. > > No, I don't think that this is happening. Parrot's slightly slower > object instantiation is due to register preserving mainly. The "__init" > code is run from inside the "new PObj, IClass" opcode. As its not known > that a method call is happening here, we can't use register preserving > operations that only save needed registers--we have to save all > registers. These two memcpys are the most heavy part of the operation.
Maybe we should rethink that then and make allocation and initialization two different phases. Or dictate that new PObj, IClass should be treated as if it were a function call with all the caller saves implications that go with it.
