Hi, once again, I'm coming up with a strange proposal: Some time ago I discussed with Uz the use of self-modifying-code (SMC) in library functions, which is today prohibited, since the code cc65 produces must be 'ROMable'. This is of course a good thing, needed and supports a general use case. But since most of my code (and I think others too) runs in RAM, I ask myself if it would make sense to introduce an additional runtime/library variant. This could be allowed to use SMC for speed & size optimization - chosen by a linker setting - just the way there are different library flavors (dynamic, static, multi-threading etc.) on other platforms too. First the SMC set would be a copy of the existing library set. Improvements could be introduced step wise and I promise to provide some of these changes. Any comments? Christian ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo@musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.Received on Tue Jan 26 08:57:29 2010
This archive was generated by hypermail 2.1.8 : 2010-01-26 08:57:33 CET