🚀 go-pugleaf

In article <17762@usc.edu> addison@pollux.usc.edu (Richard Addison) writes:
>This brings up something that I've always found horribly stupid.  I've seen
>C compilers use ext.w (followed by ext.l if ints are long) to test to see if
>a char is equal to 0, or to compare two chars, or to add, subtract two chars
>when the result will end up in a char.  These are very clearly instances of
>unnecessary promotion:  the additional high-order bits will never effect the
>lower-order bits.

The easiest way to handle C expression compilation is to always promote to
the correct size, whether or not it is necessary. It is much more difficult
to make sure that an arbitrary expression doesn't require promotion, so few
compiler writers bother to implement this special case.

Of course, The GNU C compiler probably checks. That monstrosity does
everything short of buying you a new processor to get your code as small and
efficient as possible.

-- 
Grandpa Charnock's Law:	 | C. Harald Koch  NTT Systems, Inc., Toronto, Ontario
You never really learn	 | chk@gpu.utcs.utoronto.ca	   (long-term address)
to swear until you learn | chk@zorac.dciem.dnd.ca	      (my current job)
to drive.		 | chk@chkent.UUCP		    (my AMIGA at home)