> > 	((int)val & 0x100) == 0
> > 
> > (if 'val' is signed and negative, it'll be sign-extended, so bits
> > above the low 8 will be set.  otherwise those bits will be zero.)
> 
> If we were willing to require ANSI C,
> 
> 	(signed char)val >= 0

No it wouldn't, because that would _force_ all chars to be signed,
even if the implementation's chars are by default unsigned.

The whole reason that arm32 gets that warning and ~no other ports do
is that the arm32 is an unsigned-char system.


cgd