Date: Tue, 28 Oct 1997 10:42:37 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Peter Berdeklis <peter AT atmosp DOT physics DOT utoronto DOT ca>
cc: djgpp AT delorie DOT com
Subject: Re: [Q]: unsigned char 
In-Reply-To: <Pine.SGI.3.91.971026142228.14237C-100000@atmosp.physics.utoronto.ca>
Message-ID: <Pine.SUN.3.91.971028104210.22947J-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Sun, 26 Oct 1997, Peter Berdeklis wrote:

> >   Compiler gives warning, that
> > "comparison is always 0 due to limited range of data type"
> > (no matter with or without '-funsigned-char' flag)
> 
> This appears to be a bug in DJGPP.  Compiled under gcc/SGI there is no 
> complaint.

Since when printing a warning is deemed a bug in the compiler?  The
warning here is perfectly valid, since it pinpoints a real bug in the
code (which assumed '\xFD' is an unsigned quantity), so gcc did a real
service here.

I don't know much about SGI, but it could be that the default
character type there is different from x86.  Or it could be a bug in
the SGI version of gcc.