On Saturday 23 April 2005 10:05, [EMAIL PROTECTED] wrote: > does this mean this problem is currently not fixable (and maybe "never" - > in a considerable amount of time will ?)
Correct. It may be fixable, but there's basically zero interest in fixing it. Qemu is pretty much the only place where this particular behaviour (a single ret at the end of the code) is required or even desirable. In fact the opposite is usually true - you want the fast path to be as short as possible for better cache locality. IMHO the way forward long-term is to implement some sort of code generation in qemu. By this I mean incorporating some sort of compiler backend/optimizing assembler into qemu, not just writing op.c in assembly. Obviously this is a large chunk of work. Paul _______________________________________________ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
