tag:blogger.com,1999:blog-4146794174400139442.post2457481931998010173..comments2023-07-03T07:20:53.252-04:00Comments on Whiteknight's World: YAPC: L1 RecapWhiteknighthttp://www.blogger.com/profile/16207472474429254890noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-4146794174400139442.post-10498137985361538162009-07-09T11:47:06.477-04:002009-07-09T11:47:06.477-04:00The cost of moving stuff between C and PIR is main...The cost of moving stuff between C and PIR is mainly due to the fact that Parrot's register frame is completely dynamic. The assortment and number of registers may vary in each function call. This makes easier to develop compilers but at the cost of added complexity in the interface between managed and native code. With a fixed register stack moving data between native/managed code incurs a predictable and well defined cost and JIT optimization of managed code becomes considerably easier. The complexity is then moved once again toward the compiler writer who should take responsability for optimizing register allocation. However this is not at all a new story in compiler theory and a pool of good algorithms is available to solve these problems. Why don't you chose to simplify the architecture of the VM and pretend something more from compiler writers?registerhttps://www.blogger.com/profile/02029245168545266929noreply@blogger.com