>i did this for an IDEA (encryption) routine once, and >was heartbroken to discover that it was less than a >10% increase in speed over the optimized C routine.
Very similarly for an encoder for JBIG image format. I wrote some very straightforward C code with some macros to unroll the loops, and it beat hand coded assembler. Basically, a compiler might sometimes produce better code, because it can deal with more complexity, but it will never produce a better algorithm. Of course, that argument cuts both ways. This is actually the relevant argument for computer Go. At this stage of development, advances come from better algorithms, not better code. _______________________________________________ computer-go mailing list computer-go@computer-go.org http://www.computer-go.org/mailman/listinfo/computer-go/
