Re: unsigned comparison warning

Re: unsigned comparison warning

[Manuel López-Ibáñez]

2008/7/30 Hariharan <hariharans@picochip.com>:
> Thanks Ian. I will raise this in gcc-help mailing list.

GCC versions previous to 4.3 were inconsistent. This was fixed in GCC
4.3 by grouping all similar warnings under -Wtype-limits which is
enabled by -Wextra.

See http://gcc.gnu.org/gcc-4.3/changes.html

Cheers,

Manuel.

Re: unsigned comparison warning

[Hariharan Sandanagobalane]

Thanks Manuel. I personally feel that this warning should be a part of 
-Wall.

Cheers
Hari

Manuel López-Ibáñez wrote:
> 2008/7/30 Hariharan <hariharans@picochip.com>:
>> Thanks Ian. I will raise this in gcc-help mailing list.
> 
> GCC versions previous to 4.3 were inconsistent. This was fixed in GCC
> 4.3 by grouping all similar warnings under -Wtype-limits which is
> enabled by -Wextra.
> 
> See http://gcc.gnu.org/gcc-4.3/changes.html
> 
> Cheers,
> 
> Manuel.

unsigned comparison warning

[Hariharan]

Hello,
I found something rather strange with the unsigned comparison warnings 
in GCC.

If i had,

unsigned char a; 
 

 

int foo () 
 

{ 
 

  if (a >= 0) 
 

    return 0; 
 

  else 
 

    return 1; 
 

}

and i did gcc -O2 -c trial.c, then i get a warning

trial.c:6: warning: comparison is always true due to limited range of 
data type

It works the same way if i used an unsigned short. But, if i use 
unsigned int/long, i dont get this warning. This is on x86. Is there an 
explanation for this?

I had initially tried this with 4.1.1 (default on RHE5), but Ian 
mentioned that the behaviour is the same on mainline with -Wextra.

Cheers
Hari