Hi all! In relation to a bug I entered (http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2699), I'm formulating a patch and wanted to do a quick run-by for anyone that can suggest an alternative (better) approach: It appears that XSLTC doesn't perform JVM register slot allocation in an organized fashion. Particularly, other than by reference count, there is no context for which registers can be considered in-use. With iteration, this causes problems since the next time through the loop the register could be reused and result in a type-error (bug 2699, attachment 342, template Func, instruction 63). I propose grabbing the registers that are needed for all variables and parameters in a template for the duration of a template's translation. This would be a greedy approach and would only cause problems if the number of variables + the number of parameters exceeded the number of registers in the frame (65535 I think). comments? cheers, john
