When optimizing for speed, there is also the question on how far to go. The proposed new version of print_byte_dec uses up to 213 instruction cycles. Without using assembler, for the real speed junkies, there could be the (attached) ridiculous version that only needs constant 109 cycles, independent of the input value.
Is it that version that should be compiled when "OPTIMIZE_SPEED" is set? I believe not. Greets, Kiste -- You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jallib?hl=en.
print_byte_speed.jal
Description: Binary data
