From: Leopold Toetsch <[EMAIL PROTECTED]> Date: Fri, 1 Aug 2003 14:50:05 +0200
Kenneth A Graves <[EMAIL PROTECTED]> wrote: > Inside the iterator, there are three differences compared to a function: > 1) Every register in use needs to be saved to the user stack. (Anyone > have a clean way to do this?) Its the same thing as calling a subroutine in the first place. Imcc has to figure out, which registers are used (and which are persistent over the function call). With this info the register allocation as well as the necessary register save/restore opcodes can be optimized. When this is done, the same logic applies to the .pcc_*_yield block. Is there a stub of this functionality in the code somewhere? (Or some notes about how it might be approached?) I'm either going to have to put this in the CLU compiler, or in IMCC. Advantage of the first is that I'm working in Perl instead of C. (My C is *way* rusty.) Advantage of the second is that someone else will get use out of it. --kag
