Quoting Juho Snellman <[EMAIL PROTECTED]>: > ... Either way it means that when > porting code to SBCL it's easy to see where to add those crucial > few declarations to speed the code up, while with GCL I find it > nearly impossible. DISASSEMBLE seems to always return NIL, and thus > can't be used for checking whether all the generic ops got optimized > out.
It at least used to be possible to get GCL to keep the C file the compiler made. In GCL 2.6.2 (which I just tried), disassemble works on functions that have NOT been compiled and gives both the C code and the assembly language code. -- Jeff _______________________________________________ Gcl-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gcl-devel
