Hi Uz, > That should be fixed now. The problem is the order of doing code replacements. > One order may be optimal for one case, but it may happen that another order > would be better for some other input code. So things like this may always > happen. After all, it's compiler generated, and not hand written assembly:-) Is it possible to repeat the peephole optimization until no more changes happened? Maybe this could even reduce the number of rules and make the design about the right order simple. Possibly I'm too naive... Regards, Thomas ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo@musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.Received on Sat Oct 24 12:32:55 2009
This archive was generated by hypermail 2.1.8 : 2009-10-24 12:32:57 CEST