movc3 is NOT always faster!

[Tim Bray]

x <-- USENET insecticide

When you gaily issue a movc3, there's a LOT of microcode that
starts swishing around, and also if you're assembler hacking,
you might have to push all the registers that movc* steps on.

An internal DEC benchmark I saw once suggested that movc3 becomes
a win at about 100 bytes - fewer bytes than that and a tight
mov, aobleq loop is better.

Tim Bray ...decvax!microsoft!ubc-vision!mprvaxa!tbray
         ...ihnp4!alberta!ubc-vision!mprvaxa!tbray